This bug was fixed in the package linux - 4.18.0-11.12
---
linux (4.18.0-11.12) cosmic; urgency=medium
* linux: 4.18.0-11.12 -proposed tracker (LP: #1799445)
* arm64: snapdragon: WARNING: CPU: 0 PID: 1 arch/arm64/kernel/setup.c:271
reserve_memblock_reserved_regions (LP:
This bug was fixed in the package linux - 4.18.0-11.12
---
linux (4.18.0-11.12) cosmic; urgency=medium
* linux: 4.18.0-11.12 -proposed tracker (LP: #1799445)
* arm64: snapdragon: WARNING: CPU: 0 PID: 1 arch/arm64/kernel/setup.c:271
reserve_memblock_reserved_regions (LP:
This bug was fixed in the package linux - 4.15.0-39.42
---
linux (4.15.0-39.42) bionic; urgency=medium
* linux: 4.15.0-39.42 -proposed tracker (LP: #1799411)
* Linux: insufficient shootdown for paging-structure caches (LP: #1798897)
- mm: move tlb_table_flush to
This bug was fixed in the package linux - 4.4.0-139.165
---
linux (4.4.0-139.165) xenial; urgency=medium
* linux: 4.4.0-139.165 -proposed tracker (LP: #1799401)
* Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel (LP: #1793464)
- nbd: Remove signal usage
-
** 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://bugs.launchpad.net/bugs/1797314
Title:
fscache: bad refcounting in
Yes the test results indicates that data was read cached using fscache
and 960948 ops have gone through the change.
we are not planning to test with 4.4.0-139 kernel as I don't have a
system setup for this kernel.
--
You received this bug notification because you are a member of Kernel
I have a user who confirms the 4.15.0-39 kernel fixes this issue:
# uname -a
Linux 4.15.0-39-generic #42~16.04.1-Ubuntu SMP Wed Oct 24 17:09:54
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
# cat /proc/fs/fscache/stats
FS-Cache statistics
Cookies: idx=2 dat=283731 spc=0
Objects: alc=278557 nal=0
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
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
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
** Changed in: linux (Ubuntu Xenial)
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://bugs.launchpad.net/bugs/1797314
Title:
fscache: bad refcounting in
** Changed in: linux (Ubuntu Bionic)
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://bugs.launchpad.net/bugs/1797314
Title:
fscache: bad refcounting in
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
** Description changed:
SRU Justification
-
[Impact]
A kernel BUG is sometimes observed when using fscache:
[4740718.880898] FS-Cache:
[4740718.880920] FS-Cache: Assertion failed
[4740718.880934] FS-Cache: 0 > 0 is false
[4740718.881001]
14 matches
Mail list logo
