This bug was fixed in the package linux-azure - 5.15.0-1008.9
---
linux-azure (5.15.0-1008.9) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug is awaiting verification that the linux/5.15.0-28.29 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857257
Title:
linux-image-5.0.0-35-generic breaks checkpointing of container
To manage notifications about this bug go to:
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857257
Title:
linux-image-5.0.0-35-generic breaks checkpointing of
This bug was fixed in the package linux - 5.8.0-55.62
---
linux (5.8.0-55.62) groovy; urgency=medium
* groovy/linux: 5.8.0-55.62 -proposed tracker (LP: #1930379)
* [Potential Regression] Unable to create KVM with uvtool on Groovy ARM64
(LP: #1929925)
- SAUCE: KVM: arm64:
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions --
This bug was fixed in the package linux - 5.11.0-18.19
---
linux (5.11.0-18.19) hirsute; urgency=medium
* hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578)
* Packaging resync (LP: #1786013)
- update dkms package versions
* Introduce the 465 driver series,
fine on hirsute with linux-image-5.11.0-18-generic_5.11.0-18.19_amd64
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
** Tags removed: verification-needed-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
fine on groovy linux-image-5.8.0-54-generic
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857257
Title:
fine on focal linux-image-5.4.0-74-generic_5.4.0-74.83_amd64
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857257
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857257
Title:
linux-image-5.0.0-35-generic breaks checkpointing of
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Groovy)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Hirsute)
Status:
** Patch added: "ubuntu-focal kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+attachment/5492385/+files/0001-UBUNTU-SAUCE-overlayfs-fix-incorrect-mnt_id-of-files.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The previous fix was reverted due to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690
that's weird and I can't see any logical connection between the previous fix
and problem with docker registry.
We proposed a new fix
https://lists.openvz.org/pipermail/criu/2021-April/045238.html
In the same boat as buck2202 and nfliu; we're doing some work in IBM
that uses Docker+criu so we're very interested in a fix for current LTS
releases as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Testing on google cloud, this is still broken for:
bionic hwe (5.4.0-1041-gcp #44~18.04.1-Ubuntu)
focal ga (5.4.0-1041-gcp #44-Ubuntu)
focal hwe (5.8.0-49-generic #55~20.04.1-Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It seems like there was no fix, after testing out 5.8.0-16.17 .
I also have the same question as buck2202 --- whenever a fix is
released, can we expect a backport to affected LTS kernels?
Thanks, and happy new year!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This remains an issue for the HWE kernel on 18.04LTS and GA kernel for
20.04LTS (both on kernel version 5.4). The only unaffected LTS release
is xenial.
If there is indeed a fix (which isn't clear to me from the 2020-08-26 janitor
update as it doesn't reference this bug #), will it be pushed to
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tried to re-open this bug, because we still get reports on the CRIU
side that this is not fixed:
https://github.com/checkpoint-
restore/criu/issues/860#issuecomment-668628745
We also still see this in Travis not working.
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
This bug was fixed in the package linux - 5.4.0-42.46
---
linux (5.4.0-42.46) focal; urgency=medium
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix
Dear Ubuntu kernel package "maintainers", it seems like you have somehow
managed to push *again* a kernel with this broken patch into the bionic-
proposed repo - this time, it's kernel 5.4.0-31.
Are you doing this on purpose? Kernel 5.4.0-33 with two reverted patches
*for this specific bug* and
The fixes for this bug report introduced bug 1879690 and have been
reverted on Focal and Eoan kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857257
Title:
linux-image-5.0.0-35-generic
This bug was fixed in the package linux - 5.3.0-53.47
---
linux (5.3.0-53.47) eoan; urgency=medium
* eoan/linux: 5.3.0-53.47 -proposed tracker (LP: #1877257)
* Intermittent display blackouts on event (LP: #1875254)
- drm/i915: Limit audio CDCLK>=2*BCLK constraint back to GLK
This bug was fixed in the package linux - 5.4.0-31.35
---
linux (5.4.0-31.35) focal; urgency=medium
* focal/linux: 5.4.0-31.35 -proposed tracker (LP: #1877253)
* Intermittent display blackouts on event (LP: #1875254)
- drm/i915: Limit audio CDCLK>=2*BCLK constraint back to
Fix here:
https://lists.ubuntu.com/archives/kernel-team/2020-May/109617.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857257
Title:
linux-image-5.0.0-35-generic breaks checkpointing of
The fix for this bug seems to be causing bug 1876645.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857257
Title:
linux-image-5.0.0-35-generic breaks checkpointing of container
To manage
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
Yeah, that patch is buggy and I think this might've been my fault
actually. The fix should be:
diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
index 9d16fff5342a..fbec523a67c9 100644
--- a/fs/overlayfs/file.c
+++ b/fs/overlayfs/file.c
@@ -42,6 +42,7 @@ static struct file
It seems like the patch you committed to fix this bug causes the overlay
module to crash on one of my Ubuntu 18.04 machines.
When using linux-generic 5.3.0-52.46, as soon as my gitlab-runner tries
to start up a Docker container, dmesg spits out the stuff you can see in
the "dmesg-excerpt.txt"
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag
** 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
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857257
Title:
linux-image-5.0.0-35-generic breaks checkpointing of container
To
https://lists.ubuntu.com/archives/kernel-team/2020-April/109089.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857257
Title:
linux-image-5.0.0-35-generic breaks checkpointing of container
To
Quick fix (not sure that it's fully correct)
diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
index 943733d86da3..fa30b615076e 100644
--- a/fs/overlayfs/file.c
+++ b/fs/overlayfs/file.c
@@ -24,13 +24,16 @@ static char ovl_whatisit(struct inode *inode, struct inode
*realinode)
static
Andrew absolutely right, problem introduced by commit
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe=5613773b6f576de155c39a7b7a04e45f9f6eaf46
I will try to dive into overlayfs internals and find solution.
--
You received this bug notification because
My backlog is full too and this isn't a joke:). I am out of a context of
overlayfs, so I will need to read its sources, then figure out what
change in the ubuntu kernel has introduced this issue, learn how to
compile and test the ubuntu kernel... All these could sound fun 10 years
ago, but now
On Tue, Jan 07, 2020 at 07:07:36PM -, Andrew Vagin wrote:
> The root cause of this fail is a wrong mount ID which is reported for
> file mappings:
If you have cycles to come up with a patch to fix this that would be
appreciated. Otherwise this will end up lower in my priority queue since
my
apport information
** Tags added: apport-collected eoan uec-images
** Description changed:
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
** Changed in: linux (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857257
Title:
linux-image-5.0.0-35-generic breaks checkpointing of container
To manage
The root cause of this fail is a wrong mount ID which is reported for
file mappings:
Steps to reproduce:
root@ubuntu-s-4vcpu-8gb-nyc1-01:~# uname -a
Linux ubuntu-s-4vcpu-8gb-nyc1-01 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18
05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Replying to Andrew Vagin's comment: This patch references the bug you
mentioned:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe=5613773b6f576de155c39a7b7a04e45f9f6eaf46
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The following commit looks suspicious. I don't know where I can find a
patch:
overlayfs: allow with shiftfs as underlay
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846272
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The error with 5.0.0-29-generic (and 5.0.0-27-generic), however, is
slightly different from 5.0.0-35-generic:
5.0.0-27-generic and 5.0.0-29-generic:
(00.080120) Dumping path for -3 fd via self 14 [/]
(00.080127) Error (criu/files-reg.c:1290): Unaccessible path opened 49:24201,
need 2050:547424
I can confirm that this error can not be reproduced with:
- 4.15.0-74-generic
- 4.18.0-25-generic
- 5.0.0-15-generic
- 5.0.0-20-generic
- 5.0.0-23-generic
- 5.0.0-25-generic
- 5.0.0-31-generic
- 5.0.0-32-generic
I was able to reproduce the error with 5.0.0-27-generic,
5.0.0-29-generic,
Multiple projects are now disabling CRIU tests in Travis because of this
bug:
https://github.com/containerd/containerd/pull/3898
https://github.com/opencontainers/runc/issues/2196
https://github.com/opencontainers/runc/pull/2198
** Bug watch added: github.com/opencontainers/runc/issues #2196
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857257
Title:
linux-image-5.0.0-35-generic breaks checkpointing of container
To
53 matches
Mail list logo
