This bug was fixed in the package linux - 4.4.0-143.169
---
linux (4.4.0-143.169) xenial; urgency=medium
* linux: 4.4.0-143.169 -proposed tracker (LP: #1814647)
* x86/kvm: Backport fixup and missing commits (LP: #1811646)
- KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
This bug was fixed in the package linux - 3.13.0-166.216
---
linux (3.13.0-166.216) trusty; urgency=medium
* linux: 3.13.0-166.216 -proposed tracker (LP: #1814645)
* linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] limit preparat
This bug was fixed in the package linux - 4.18.0-16.17
---
linux (4.18.0-16.17) cosmic; urgency=medium
* linux: 4.18.0-16.17 -proposed tracker (LP: #1814749)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* CVE-2018-16880
- vhost: fix OOB in get_
This bug was fixed in the package linux - 4.18.0-16.17
---
linux (4.18.0-16.17) cosmic; urgency=medium
* linux: 4.18.0-16.17 -proposed tracker (LP: #1814749)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* CVE-2018-16880
- vhost: fix OOB in get_
This bug was fixed in the package linux - 4.15.0-46.49
---
linux (4.15.0-46.49) bionic; urgency=medium
* linux: 4.15.0-46.49 -proposed tracker (LP: #1814726)
* mprotect fails on ext4 with dax (LP: #1799237)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
* kernel
For documentation purposes, this is the block device setup
configured in the system to debug/test/fix/verify the bug.
disk partitioning:
# fdisk /dev/sdb # create sdb1 and sbd2, 100G each.
bcache backing device: LVM volume in partition 1
# pvcreate /dev/sdb1
# vgcreate vg-test /dev/sdb1
# lvcre
trusty-proposed:
---
verification successful.
executed the reproducer 3x on the system used to debug/test/fix this problem.
no bug/oops observed.
root@petilil:~# uname -rv
3.13.0-166-generic #216-Ubuntu SMP Thu Feb 7 14:07:53 UTC 2019
root@petilil:~# echo writeback > /sys/block/bcache0/bcache/ca
xenial-proposed:
---
verification successful.
executed the reproducer 3x on the system used to debug/test/fix this problem.
no bug/oops observed.
root@petilil:~# uname -rv
4.4.0-143-generic #169-Ubuntu SMP Thu Feb 7 07:56:38 UTC 2019
root@petilil:~# echo writeback > /sys/block/bcache0/bcache/ca
bionic-proposed:
---
verification successful.
executed the reproducer 3x on the system used to debug/test/fix this problem.
no bug/oops observed.
root@petilil:~# uname -rv
4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019
root@petilil:~# echo writeback > /sys/block/bcache0/bcache/cach
cosmic-proposed:
---
verification successful.
executed the reproducer 3x on the system used to debug/test/fix this problem.
no bug/oops observed.
root@petilil:~# uname -rv
4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019
root@petilil:~# echo writeback > /sys/block/bcache0/bcache/cach
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-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
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-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verifica
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-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug was fixed in the package linux - 4.19.0-12.13
---
linux (4.19.0-12.13) disco; urgency=medium
* linux: 4.19.0-12.13 -proposed tracker (LP: #1813664)
* kernel oops in bcache module (LP: #1793901)
- SAUCE: bcache: never writeback a discard operation
* Disco update: 4
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Cosmic)
Status: New =>
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Trusty)
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/
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Trusty)
Importance: Undeci
So any idea when the backport will drop?
--
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/1793901
Title:
kernel oops in bcache module
Status in linux package in Ubuntu:
Fix Committed
B
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1793901
Title:
kernel oops in bcache module
Status in linux packag
** Description changed:
+ SRU Justification
+ =
+
+ [Impact]
+
+ Some users see panics like the following when performing fstrim on a
+ bcached volume:
+
+ [ 529.803060] BUG: unable to handle kernel NULL pointer dereference at
0008
+ [ 530.183928] #PF error: [norm
Hi,
I have a patch which I believe fixes your issue:
https://www.spinics.net/lists/linux-bcache/msg06997.html
It looks like it will go in to the 5.1 kernel, and I will propose it for
backporting to earlier Ubuntu kernels.
Regards,
Daniel
--
You received this bug notification because you are a
I think I have discovered the cause: https://lore.kernel.org/linux-
block/87h8e9ii2l@linkitivity.dja.id.au/
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
We have a reproducer now:
$ uname -a
Linux ln-sv-infr01 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
$ lsblk
NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 3.7T 0 disk
├─sda1
Hello step21,
I can replicate your bug with fstrim -a command. Can you please try it (save
your work before)?
In fact, bug reproduces itself in a weekly bases thanks to fstrim systemd
timer. Timer can be disabled with: sudo systemctl disable fstrim.timer command.
In my understanding, fstrim tr
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Tags added: invalid
--
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/1793901
Title:
kernel oops in bcache module
Status in linux package in Ubuntu:
Incomplete
Bug description:
Thi
My system has changed somewhat, as I moved my root / to bcache with a kernel
that worked.
Still, I installed the mainline build, and the oops did not occur so far.
However I also cannot run that kernel properly as it does not seem to work well
with Nvidia graphics. (very low resolution and proba
My system has changed somewhat, as I moved my root / to bcache with a kernel
that worked.
Still, I installed the mainline build, and the oops did not occur so far.
However I also cannot run that kernel properly as it does not seem to work well
with Nvidia graphics. (very low resolution and proba
My system has changed somewhat, as I moved my root / to bcache with a kernel
that worked.
Still, I installed the mainline build, and the oops did not occur so far.
However I also cannot run that kernel properly as it does not seem to work well
with Nvidia graphics. (very low resolution and proba
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
https://launchpad.net/ubuntu/+source/linux/4.15.0-34.37
--
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/1793901
Title:
kernel oops in bcache module
Status in linux package in Ubuntu:
C
It seems that this might be only a problem with linux-image-4.15.0-34-generic
I tested it now with linux-image-4.15.0-34-generic and 4.18.0 (self compiled)
and in both cases the oops didn't trigger after a reasonable amount of time.
When checking the changelog for -34 it seems there was a change r
repost with ubuntu-bug and for different package as this one might be
more generally applicable. This is also reproducible, happens each time
sometime after mount, even after a reboot. New crash log is attached.
** Attachment added: "linux-image-4.15.0-34-generic.0.crash"
https://bugs.launchpa
35 matches
Mail list logo
