[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-10-13 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-51.56 --- linux (5.4.0-51.56) focal; urgency=medium * Packaging resync (LP: #1786013) - update dkms package versions linux (5.4.0-50.55) focal; urgency=medium * CVE-2020-16119 - SAUCE: dccp: avoid double free of ccid on chi

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-10-09 Thread Ian
I've confirmed using William's provided steps that the crash no longer occurs on 5.4.0-49.53 ** 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://bug

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-10-08 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.8.0-21.22 --- linux (5.8.0-21.22) groovy; urgency=medium * groovy/linux: 5.8.0-21.22 -proposed tracker (LP: #1898150) * Packaging resync (LP: #1786013) - update dkms package versions * Fix broken e1000e device after S3 (LP: #1897

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-10-06 Thread Ian
Hi William, We are working to get verification testing completed, would you be able to confirm this issue no longer occurs in 5.4.0-49.53. Thanks, Ian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/18

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-09-21 Thread Ubuntu Kernel Bot
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

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-09-17 Thread Ian
** Changed in: linux (Ubuntu Focal) Status: New => 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/1894780 Title: Oops and hang when starting LVM snapshots on 5.4.0-47 To manage

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-09-16 Thread Thadeu Lima de Souza Cascardo
** Description changed: + [Impact] + kmemcaches will fail to be created after they have just been removed but not completely ripped out. This will cause some drivers (like lvm snapshots) to properly work and cause kernel traces to go on the logs. + + [Test case] + See comment #9. + + [Regressi

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-09-16 Thread Thadeu Lima de Souza Cascardo
After reverting commit 79ffe7107b13042c69c4a06394175362121b06b5 (upstream commit d38a2b7a9c939e6d7329ab92b96559ccebf7b135) ("mm: memcg/slab: fix memory leak at non-root kmem_cache destroy"), things seem to go back to normal. The probable reason this one causes a problem is because it has: @@ -326

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-09-10 Thread William Grant
As expected, it's easy enough to repro with raw dm_snapshot: root@bug-1894780-focal-3:~# for f in base snap1 snap2; do dd if=/dev/zero of=$f.img bs=1M count=1 seek=512; done root@bug-1894780-focal-3:~# losetup -f base.img root@bug-1894780-focal-3:~# losetup -f snap1.img root@bug-1894780

Re: [Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-09-09 Thread William Grant
On 10/9/20 7:44 am, Jay Vosburgh wrote: > wgrant, you said: > > That :a-152 is meant to be /sys/kernel/slab/:a-152. Even a > working kernel shows some trouble there: > > $ uname -a > Linux 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 > 07:21:24 UTC 2020 x86_64 x86_64 x86_64 GN

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-09-09 Thread Jay Vosburgh
wgrant, you said: That :a-152 is meant to be /sys/kernel/slab/:a-152. Even a working kernel shows some trouble there: $ uname -a Linux 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ ls -l /sys/kernel/slab | grep a-152 lr

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-09-08 Thread William Grant
https://lore.kernel.org/linux- mm/alpine.lrh.2.02.1806151817130.6...@file01.intranet.prod.int.rdu2.redhat.com/ (2018's "slub: fix failure when we delete and create a slab cache") looks relevant to similar problems with this particular slub callsite. -- You received this bug notification because y

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-09-08 Thread William Grant
[ 31.566946] kobject_add_internal failed for :a-152 with -EEXIST, don't try to register things with the same name in the same directory. [ 31.580027] BUG: kernel NULL pointer dereference, address: 0020 [ 31.586990] #PF: supervisor read access in kernel mode [ 31.592130] #PF

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-09-08 Thread Kleber Sacilotto de Souza
Hi William, Could you please test with the HWE 5.4.0-45.49~18.04.2 kernel? ** Also affects: linux (Ubuntu Focal) 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/b

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-09-07 Thread Andy Whitcroft
** 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/1894780 Title: Oops and hang when starting LVM snapshots on 5.4.0-47 To manage not