** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Eoan)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1857257
Title:
linux-image-5.0.0-35-generic breaks checkpointing of container
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
Trying to checkpoint a container (docker/podman) on 18.04 fails
starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see
this in Travis starting a few weeks ago. Manually testing it locally
shows that linux-image-5.0.0-32-generic still works and linux-
image-5.0.0-35-generic does not longer work. It seems to be overlayfs
related, at least that is what we believe. The CRIU error message we
see is:
(00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3
path=/bin/busybox
(00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed
with -1
We have not seen this only in Travis, but also multiple CRIU users reported
that bug already. Currently we have to tell them to downgrade the kernel.
I also able to reproduce it with linux-image-5.3.0-24-generic. Staying
on the 4.18.0 kernel series does not show this error.
4.18.0-25-generic works without problems.
See also https://github.com/checkpoint-restore/criu/issues/860
One of the possible explanations from our side include:
"Looks like we have the same as for st_dev now with mnt_id, that is
bad, because we can't find on which mount to open the file if kernel
hides these information from us."
Running on the upstream 5.5.0-rc1 kernel does not show this error.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Jan 7 18:52 seq
crw-rw---- 1 root audio 116, 33 Jan 7 18:52 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 19.10
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: DigitalOcean Droplet
Package: linux (not installed)
PciMultimedia:
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic
root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
RelatedPackageVersions:
linux-restricted-modules-5.3.0-26-generic N/A
linux-backports-modules-5.3.0-26-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: eoan uec-images
Uname: Linux 5.3.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 12/12/2017
dmi.bios.vendor: DigitalOcean
dmi.bios.version: 20171212
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr:
dmi.product.family: DigitalOcean_Droplet
dmi.product.name: Droplet
dmi.product.version: 20171212
dmi.sys.vendor: DigitalOcean
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
