This bug was fixed in the package linux - 5.10.0-14.15
---
linux (5.10.0-14.15) hirsute; urgency=medium
* hirsute/linux: 5.10.0-14.15 -proposed tracker (LP: #1913724)
* Restore palm ejection on multi-input devices (LP: #1913520)
- HID: multitouch: Apply MT_QUIRK_CONFIDENCE qu
This bug was fixed in the package linux - 5.8.0-41.46
---
linux (5.8.0-41.46) groovy; urgency=medium
* groovy/linux: 5.8.0-41.46 -proposed tracker (LP: #1912219)
* Groovy update: upstream stable patchset 2020-12-17 (LP: #1908555) // nvme
drive fails after some time (LP: #1910
This bug was fixed in the package linux - 5.4.0-65.73
---
linux (5.4.0-65.73) focal; urgency=medium
* focal/linux: 5.4.0-65.73 -proposed tracker (LP: #1912220)
* initramfs unpacking failed (LP: #1835660)
- SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around
i
Thanks!
>> I noticed that in the list of affected packages in the bug metadata
>> Bionic is not mentioned. Will the fix also be backported there?
>
> It depends on which kernel you are talking about. The bionic GA kernel
> (4.15) was not affected based on my testing. If you are seeing problems
> w
Confirmed that the attached test script reproduces the problem with
5.8.0-36-generic from groovy-updates. ith 5.8.0-37-generic from groovy-
proposed the problem is fixed.
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification bec
On Mon, Jan 11, 2021 at 11:12:35AM -, Philipp Wendler wrote:
> I tested it on a Focal machine and the -proposed kernel works. However,
> I don't have a Groovy machine here, is it necessary for me to test this?
I can verify the fix in groovy.
> I noticed that in the list of affected packages i
Thanks!
I tested it on a Focal machine and the -proposed kernel works. However,
I don't have a Groovy machine here, is it necessary for me to test this?
I noticed that in the list of affected packages in the bug metadata
Bionic is not mentioned. Will the fix also be backported there?
** Tags rem
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 'verificati
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 'verifica
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1900141
Title:
overlay: permission regression in 5.4.0-51.56 due to patches re
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Thanks Seth - that appears to fix our problem as well!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900141
Title:
overlay: permission regression in 5.4.0-51.56 due to patches related
to CVE-2020
** Description changed:
+ SRU Justification
+
+ [Impact]
+
+ The backports to fix CVE-2020-16120 introduced a regression for overlay
+ mounts within user namespaces. Files with ownership outside of the user
+ namespace can no longer be accessed, even if allowed by both DAC and
+ MAC.
+
+ This i
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux (Ubuntu Focal)
Status: New => In P
Apologies for the delay on this bug. There is a fix upstream in
5.11-rc1, I've backported the fix to the test kernel located here:
https://people.canonical.com/~sforshee/lp1900141/linux-5.4.0-59.65+lp1900141v202101061102/
I'm also attaching a script which reproduces the bug. In my testing the
pro
This also breaks some of our containers - is there any kind of work-
around we can use?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900141
Title:
overlay: permission regression in 5.4.0-51.56 due
I noticed that the changelog of the kernel package 5.4.0-50.55~18.04.1
for Bionic now also includes the two additional patches, and indeed I
can confirm that on Bionic with kernel 5.4.0-54-generic the regression
was now also introduced.
Is there an update whether it will be possible to solve this
I think I see what the problem is, one of the patches adds a check that
is probably unnecessary and too restrictive. This is an upstream issue
though, so I'm going to follow up with the upstream developers to ensure
there isn't a good reason for the check that isn't apparent to me.
** Changed in:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900141
Title:
over
19 matches
Mail list logo