Like https://bugzilla.redhat.com/show_bug.cgi?id=2347256 The kernel update to 6.13 seems to have broken criu on f40. criu log: ... (44.595634) Error (criu/vdso.c:381): vdso: Unexpected rt vDSO area bounds (44.595636) Error (criu/vdso.c:613): vdso: Failed to fill self vdso symtable (44.595637) Error (criu/kerndat.c:1906): kerndat_vdso_fill_symtable failed when initializing kerndat. Reproducible: Always Steps to Reproduce: 1. podman run --name test -d quay.io/libpod/testimage:20241011 top 2. podman container checkpoint test Actual Results: 2025-03-27T11:30:28.047884Z: CRIU checkpointing failed -52. Please check CRIU logfile /var/lib/containers/storage/overlay-containers/f67260bffe9ef1fe636bb8411fedf89f4601c49187c507cc172b260d144941e0/userdata/dump.log: Invalid exchange Error: `/usr/bin/crun checkpoint --image-path /var/lib/containers/storage/overlay-containers/f67260bffe9ef1fe636bb8411fedf89f4601c49187c507cc172b260d144941e0/userdata/checkpoint --work-path /var/lib/containers/storage/overlay-containers/f67260bffe9ef1fe636bb8411fedf89f4601c49187c507cc172b260d144941e0/userdata f67260bffe9ef1fe636bb8411fedf89f4601c49187c507cc172b260d144941e0` failed: exit status 1 Expected Results: checkpoint works criu-4.0-1.fc40.x86_64 kernel-6.13.6-100.fc40.x86_64 podman-5.4.0-1.fc40.x86_64
This problem has been reported upstream: - https://github.com/checkpoint-restore/criu/issues/2626 - https://lore.kernel.org/criu/zihwmp67m2lpuxbfktmztvjdyap7suzd75dowlw4eamu6bhjf3@6euydiqowc7h/T/#u The fix requires kernel patch and changes to CRIU: - https://lore.kernel.org/linux-fsdevel/20250320063903.2685882-1-avagin@google.com/
Is that really the case? AFAICT this is the exact same symptom from https://bugzilla.redhat.com/show_bug.cgi?id=2347256 and https://bugzilla.redhat.com/show_bug.cgi?id=2328985 which was patched in criu and seems to be working now on f41/rawhide. My guess was that the fix was just never backported to f40? full dump.log: (00.000000) Unable to get $HOME directory, local configuration file will not be used. (00.000026) Version: 4.0 (gitid 0) (00.000030) Running on vm-10-0-186-175.hosted.upshift.rdu2.redhat.com Linux 6.13.6-100.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Mar 7 21:23:12 UTC 2025 x86_64 (00.000514) File /run/criu/criu.kdat does not exist (00.001024) sockets: Probing sock diag modules (00.001077) sockets: Done probing (00.004362) PAGEMAP_SCAN is supported (00.004378) Pagemap is fully functional (00.004406) Found anon-shmem device at 1 (00.004501) Hugetlb size 2 Mb is supported but cannot get dev's number (00.004514) Hugetlb size 1024 Mb is supported but cannot get dev's number (00.004517) Reset 2861's dirty tracking (00.004583) ... done (00.004601) Dirty track supported on kernel (00.004659) Found task size of 7ffffffff000 (00.018916) net: Restoring netdev veth idx 10 (00.019155) net: Dumping netns links (00.019178) net: LD: Got link 1, type 772 (00.019180) net: LD: Got link 10, type 1 (44.595599) vdso: Parsing at 7f740a424000 7f740a426000 (44.595623) vdso: PT_LOAD p_vaddr: 0 (44.595625) vdso: DT_HASH: 120 (44.595626) vdso: DT_STRTAB: 340 (44.595627) vdso: DT_SYMTAB: 1d8 (44.595629) vdso: DT_STRSZ: 9c (44.595630) vdso: DT_SYMENT: 18 (44.595631) vdso: nbucket 3 nchain f bucket 7f740a424128 chain 7f740a424134 (44.595634) Error (criu/vdso.c:381): vdso: Unexpected rt vDSO area bounds (44.595636) Error (criu/vdso.c:613): vdso: Failed to fill self vdso symtable (44.595637) Error (criu/kerndat.c:1906): kerndat_vdso_fill_symtable failed when initializing kerndat. (44.595821) Found mmap_min_addr 0x10000 (44.595932) files stat: fs/nr_open 1073741816
FEDORA-2025-ef25dec09e (criu-4.1-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2025-ef25dec09e
FEDORA-2025-ef25dec09e has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-ef25dec09e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-ef25dec09e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-dec654d428 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-dec654d428` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-dec654d428 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
FEDORA-2025-dec654d428 (criu-4.1-2.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.