--- Begin Message ---
Package: src:linux
Version: 4.19.67-2+deb10u2
Severity: normal
Tags: upstream
Dear Maintainer,
we are affected by a regression the buster (security) kernel.
The problem manifests itself when building multiple docker containers
concurrently. (We are using a non-debian docker package).
The original issue has been reported https://github.com/moby/moby/issues/39475.
A kernel fix has been shipped in 4.19.75, 5.2.17 and 5.3.1 kernels,
unfortunately the Buster kernel is still at 4.19.67.
Would it be possible to bump the buster kernel to a more recent stable
release?
Thanks,
Thomas
-- Package-specific info:
** Version:
Linux version 4.19.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11)
** Command line:
initrd=\linux\initrd.img-4.19.0-6-amd64 root=UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rw vsyscall=emulate
** Not tainted
** Kernel log:
...
[Tue Feb 4 13:36:41 2020] overlayfs: workdir is in-use by another mount, accessing files from both mounts will result in undefined behavior.
[Tue Feb 4 13:36:11 2020] overlayfs: upperdir is in-use by another mount, accessing files from both mounts will result in undefined behavior.
[Tue Feb 4 13:36:11 2020] overlayfs: workdir is in-use by another mount, accessing files from both mounts will result in undefined behavior.
[Tue Feb 4 13:36:41 2020] overlayfs: upperdir is in-use by another mount, accessing files from both mounts will result in undefined behavior.
[Tue Feb 4 13:36:41 2020] overlayfs: workdir is in-use by another mount, accessing files from both mounts will result in undefined behavior.
...
** Model information
sys_vendor: VMware, Inc.
product_name: VMware7,1
product_version: None
chassis_vendor: No Enclosure
chassis_version: N/A
bios_vendor: VMware, Inc.
bios_version: VMW71.00V.0.B64.1809080740
board_vendor: Intel Corporation
board_name: 440BX Desktop Reference Platform
board_version: None
** Loaded modules:
redacted
** PCI devices:
redacted
** USB devices:
not available
-- System Information:
Debian Release: 10.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages linux-image-4.19.0-6-amd64 depends on:
ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1
ii kmod 26-1
ii linux-base 4.6
Versions of packages linux-image-4.19.0-6-amd64 recommends:
pn apparmor <none>
pn firmware-linux-free <none>
Versions of packages linux-image-4.19.0-6-amd64 suggests:
pn debian-kernel-handbook <none>
pn grub-pc | grub-efi-amd64 | extlinux <none>
pn linux-doc-4.19 <none>
Versions of packages linux-image-4.19.0-6-amd64 is related to:
pn firmware-amd-graphics <none>
pn firmware-atheros <none>
pn firmware-bnx2 <none>
pn firmware-bnx2x <none>
pn firmware-brcm80211 <none>
pn firmware-cavium <none>
pn firmware-intel-sound <none>
pn firmware-intelwimax <none>
pn firmware-ipw2x00 <none>
pn firmware-ivtv <none>
pn firmware-iwlwifi <none>
pn firmware-libertas <none>
pn firmware-linux-nonfree <none>
pn firmware-misc-nonfree <none>
pn firmware-myricom <none>
pn firmware-netxen <none>
pn firmware-qlogic <none>
pn firmware-realtek <none>
pn firmware-samsung <none>
pn firmware-siano <none>
pn firmware-ti-connectivity <none>
pn xen-hypervisor <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.19.87-1
Hi,
On Tue, Feb 04, 2020 at 03:48:46PM +0000, Thomas Weißschuh wrote:
> Package: src:linux
> Version: 4.19.67-2+deb10u2
> Severity: normal
> Tags: upstream
>
> Dear Maintainer,
>
> we are affected by a regression the buster (security) kernel.
> The problem manifests itself when building multiple docker containers
> concurrently. (We are using a non-debian docker package).
>
> The original issue has been reported https://github.com/moby/moby/issues/39475.
>
> A kernel fix has been shipped in 4.19.75, 5.2.17 and 5.3.1 kernels,
> unfortunately the Buster kernel is still at 4.19.67.
>
> Would it be possible to bump the buster kernel to a more recent stable
> release?
This is alredy the case for the upcoming point release on next
weekend, which will have the version updated to 4.19.98-1. Closing
this issue accordingly already to track the fixed version.
Regards,
Salvatore
--- End Message ---