Setting to 'Confirmed' as the issue was fixed upstream and this is a
backport request.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- bcache device is accessible even if a backing device is not (writeback mode)
+ [4.15] bcache device is accessible even if a backing device is not (writeback
mode)
--
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/1829563
Title:
[4.15] bcache device is accessible even if a backing device is not
(writeback mode)
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a request for a backport of the following upstream patch from
4.18:
"bcache: stop bcache device when backing device is offline"
https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee
Field engineering uses bcache quite extensively and it would be good
to have this in the GA/bionic kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
