mirror of
https://github.com/checkpoint-restore/criu.git
synced 2026-07-17 16:47:50 +00:00
fc29bfef9d
CRIU dumps and restores the SO_SNDTIMEO and SO_RCVTIMEO socket send/receive timeout options in dump_socket_opts()/restore_socket_opts() (criu/sockets.c), but the ZDTM suite has no dedicated coverage for them: SO_SNDTIMEO is not exercised by any test, and SO_RCVTIMEO is only used incidentally as a receive timeout in socket_icmp, never asserted across checkpoint/restore. Add socket-timeo, which sets distinct send and receive timeouts on a socket, performs checkpoint/restore, and verifies both values survive. Whole-second timeouts are used because the kernel stores these options with jiffy granularity: setsockopt() may round a sub-second value to the nearest tick depending on HZ, so a literal sub-second expectation could fail to match the stored value regardless of checkpoint/restore. The send and receive values differ so a mix-up between the two options is caught. Assisted-by: Claude:claude-opus-4-8 Signed-off-by: Rocker Zhang <zhang.rocker.liyuan@gmail.com> |
||
|---|---|---|
| .. | ||
| compel | ||
| cuda-checkpoint | ||
| exhaustive | ||
| inhfd | ||
| javaTests | ||
| jenkins | ||
| libfault | ||
| others | ||
| pki | ||
| plugins | ||
| zdtm | ||
| .gitignore | ||
| abrt.sh | ||
| crit-recode.py | ||
| empty-netns-prep.sh | ||
| groups.desc | ||
| inhfd.desc | ||
| Makefile | ||
| pycriu | ||
| umount2.c | ||
| zdtm.desc | ||
| zdtm.py | ||
| zdtm_ct.c | ||
| zdtm_mount_cgroups | ||
| zdtm_umount_cgroups | ||