| 2019-05-17 16:46:59 |
Dmitrii Shcherbakov |
bug |
|
|
added bug |
| 2019-05-17 17:00:06 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2019-05-17 17:07:43 |
Dmitrii Shcherbakov |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2019-05-17 17:08:22 |
Dmitrii Shcherbakov |
summary |
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) |
|
| 2019-05-18 00:11:07 |
Mauricio Faria de Oliveira |
linux (Ubuntu): assignee |
|
Mauricio Faria de Oliveira (mfo) |
|
| 2019-05-20 16:48:29 |
Felipe Reyes |
bug |
|
|
added subscriber Felipe Reyes |
| 2019-05-20 21:41:23 |
Terry Rudd |
bug |
|
|
added subscriber Terry Rudd |
| 2019-05-22 08:08:27 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2019-05-23 09:19:34 |
Dominique Poulain |
bug |
|
|
added subscriber Dominique Poulain |
| 2019-06-22 16:21:13 |
Mauricio Faria de Oliveira |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-06-22 16:21:13 |
Mauricio Faria de Oliveira |
bug task added |
|
linux (Ubuntu Cosmic) |
|
| 2019-06-22 16:21:13 |
Mauricio Faria de Oliveira |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-06-22 16:21:13 |
Mauricio Faria de Oliveira |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2019-06-22 16:21:24 |
Mauricio Faria de Oliveira |
linux (Ubuntu Bionic): assignee |
|
Mauricio Faria de Oliveira (mfo) |
|
| 2019-06-22 16:21:28 |
Mauricio Faria de Oliveira |
linux (Ubuntu Cosmic): assignee |
|
Mauricio Faria de Oliveira (mfo) |
|
| 2019-06-22 16:21:35 |
Mauricio Faria de Oliveira |
linux (Ubuntu Cosmic): status |
New |
In Progress |
|
| 2019-06-22 16:21:40 |
Mauricio Faria de Oliveira |
linux (Ubuntu Bionic): status |
New |
In Progress |
|
| 2019-06-22 16:21:45 |
Mauricio Faria de Oliveira |
linux (Ubuntu): status |
Confirmed |
Invalid |
|
| 2019-06-22 17:04:47 |
Mauricio Faria de Oliveira |
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. |
[Impact]
* The bcache code in Bionic lacks several fixes to handle
I/O errors in both backing devices and caching devices.
* Partial or permanent errors in backing or caching devices,
specially in writeback mode, can lead to data loss and/or
the application is not notified about failed I/O requests.
* The bcache device might remain available for I/O requests
even if backing device is offline, so writes are undefined.
[Test Case]
* Detailed test cases/steps for the behavior of almost every
patch with code logic changes are provided in bug comments.
* The patchset has been tested for regressions on each cache
mode (writethrough, writeback, writearound, none) with the
xfstests test suite (on ext4), fio (random read-write) and
iozone (several read/write tests).
[Regression Potential]
* The patchset is relatively large and touches several areas
in bcache code, however, synthetic testing of the patches
has been performed, and extensive regression/stress tests
were run (as mentioned in Test Case section).
* Many patches in the patchset are 'Fixes' patches to other
patches, and no further 'Fixes' currently exist upstream.
[Other Info]
* Canonical Field Eng. deploys bcache+writeback extensively
(e.g., BootStack, UA cloud, except rare all-flash cases).
[Original 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. |
|
| 2019-06-22 17:05:04 |
Mauricio Faria de Oliveira |
summary |
[4.15] bcache device is accessible even if a backing device is not (writeback mode) |
bcache: risk of data loss on I/O errors in backing or caching devices |
|
| 2019-07-07 23:44:12 |
Mauricio Faria de Oliveira |
attachment added |
|
test-bcache-cache-modes.xfstests.sh https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275531/+files/test-bcache-cache-modes.xfstests.sh |
|
| 2019-07-07 23:51:29 |
Mauricio Faria de Oliveira |
attachment added |
|
test-bcache-cache-modes.fio.sh https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275532/+files/test-bcache-cache-modes.fio.sh |
|
| 2019-07-08 00:04:04 |
Mauricio Faria de Oliveira |
attachment added |
|
setup.sh https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275533/+files/setup.sh |
|
| 2019-07-08 00:04:14 |
Mauricio Faria de Oliveira |
attachment added |
|
setup-sda.sh https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275534/+files/setup-sda.sh |
|
| 2019-07-08 00:04:28 |
Mauricio Faria de Oliveira |
attachment added |
|
setup-two-bcache-one-cache.sh https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275535/+files/setup-two-bcache-one-cache.sh |
|
| 2019-07-08 00:43:12 |
Mauricio Faria de Oliveira |
description |
[Impact]
* The bcache code in Bionic lacks several fixes to handle
I/O errors in both backing devices and caching devices.
* Partial or permanent errors in backing or caching devices,
specially in writeback mode, can lead to data loss and/or
the application is not notified about failed I/O requests.
* The bcache device might remain available for I/O requests
even if backing device is offline, so writes are undefined.
[Test Case]
* Detailed test cases/steps for the behavior of almost every
patch with code logic changes are provided in bug comments.
* The patchset has been tested for regressions on each cache
mode (writethrough, writeback, writearound, none) with the
xfstests test suite (on ext4), fio (random read-write) and
iozone (several read/write tests).
[Regression Potential]
* The patchset is relatively large and touches several areas
in bcache code, however, synthetic testing of the patches
has been performed, and extensive regression/stress tests
were run (as mentioned in Test Case section).
* Many patches in the patchset are 'Fixes' patches to other
patches, and no further 'Fixes' currently exist upstream.
[Other Info]
* Canonical Field Eng. deploys bcache+writeback extensively
(e.g., BootStack, UA cloud, except rare all-flash cases).
[Original 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. |
[Impact]
* The bcache code in Bionic lacks several fixes to handle
I/O errors in both backing devices and caching devices.
* Partial or permanent errors in backing or caching devices,
specially in writeback mode, can lead to data loss and/or
the application is not notified about failed I/O requests.
* The bcache device might remain available for I/O requests
even if backing device is offline, so writes are undefined.
[Test Case]
* Detailed test cases/steps for the behavior of almost every
patch with code logic changes are provided in bug comments.
* The patchset has been tested for regressions on each cache
mode (writethrough, writeback, writearound, none) with the
xfstests test suite (on ext4) and fio (sequential + random
read-write).
[Regression Potential]
* The patchset is relatively large and touches several areas
in bcache code, however, synthetic testing of the patches
has been performed, and extensive regression/stress tests
were run (as mentioned in Test Case section).
* Many patches in the patchset are 'Fixes' patches to other
patches, and no further 'Fixes' currently exist upstream.
[Other Info]
* Canonical Field Eng. deploys bcache+writeback extensively
(e.g., BootStack, UA cloud, except rare all-flash cases).
[Original 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. |
|
| 2019-07-08 00:44:21 |
Mauricio Faria de Oliveira |
description |
[Impact]
* The bcache code in Bionic lacks several fixes to handle
I/O errors in both backing devices and caching devices.
* Partial or permanent errors in backing or caching devices,
specially in writeback mode, can lead to data loss and/or
the application is not notified about failed I/O requests.
* The bcache device might remain available for I/O requests
even if backing device is offline, so writes are undefined.
[Test Case]
* Detailed test cases/steps for the behavior of almost every
patch with code logic changes are provided in bug comments.
* The patchset has been tested for regressions on each cache
mode (writethrough, writeback, writearound, none) with the
xfstests test suite (on ext4) and fio (sequential + random
read-write).
[Regression Potential]
* The patchset is relatively large and touches several areas
in bcache code, however, synthetic testing of the patches
has been performed, and extensive regression/stress tests
were run (as mentioned in Test Case section).
* Many patches in the patchset are 'Fixes' patches to other
patches, and no further 'Fixes' currently exist upstream.
[Other Info]
* Canonical Field Eng. deploys bcache+writeback extensively
(e.g., BootStack, UA cloud, except rare all-flash cases).
[Original 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. |
[Impact]
* The bcache code in Bionic lacks several fixes to handle
I/O errors in both backing devices and caching devices.
* Partial or permanent errors in backing or caching devices,
specially in writeback mode, can lead to data loss and/or
the application is not notified about failed I/O requests.
* The bcache device might remain available for I/O requests
even if backing device is offline, so writes are undefined.
[Test Case]
* Detailed test cases/steps for the behavior of many patches
with code logic changes are provided in bug comments.
* The patchset has been tested for regressions on each cache
mode (writethrough, writeback, writearound, none) with the
xfstests test suite (on ext4) and fio (sequential + random
read-write).
[Regression Potential]
* The patchset is relatively large and touches several areas
in bcache code, however, synthetic testing of the patches
has been performed, and extensive regression/stress tests
were run (as mentioned in Test Case section).
* Many patches in the patchset are 'Fixes' patches to other
patches, and no further 'Fixes' currently exist upstream.
[Other Info]
* Canonical Field Eng. deploys bcache+writeback extensively
(e.g., BootStack, UA cloud, except rare all-flash cases).
[Original 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. |
|
| 2019-07-08 14:41:44 |
Mauricio Faria de Oliveira |
nominated for series |
|
Ubuntu Eoan |
|
| 2019-07-08 14:41:44 |
Mauricio Faria de Oliveira |
bug task added |
|
linux (Ubuntu Eoan) |
|
| 2019-07-08 14:41:44 |
Mauricio Faria de Oliveira |
nominated for series |
|
Ubuntu Disco |
|
| 2019-07-08 14:41:44 |
Mauricio Faria de Oliveira |
bug task added |
|
linux (Ubuntu Disco) |
|
| 2019-07-08 14:41:53 |
Mauricio Faria de Oliveira |
linux (Ubuntu Disco): status |
New |
In Progress |
|
| 2019-07-08 14:41:59 |
Mauricio Faria de Oliveira |
linux (Ubuntu Eoan): status |
Invalid |
In Progress |
|
| 2019-07-17 10:03:55 |
Kleber Sacilotto de Souza |
linux (Ubuntu Cosmic): status |
In Progress |
Won't Fix |
|
| 2019-07-17 10:04:39 |
Kleber Sacilotto de Souza |
linux (Ubuntu Disco): assignee |
|
Mauricio Faria de Oliveira (mfo) |
|
| 2019-07-17 10:46:00 |
Kleber Sacilotto de Souza |
linux (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2019-07-17 16:12:14 |
Seth Forshee |
linux (Ubuntu Eoan): status |
In Progress |
Fix Committed |
|
| 2019-07-18 09:11:23 |
Stefan Bader |
linux (Ubuntu Disco): importance |
Undecided |
Medium |
|
| 2019-07-18 09:11:32 |
Stefan Bader |
linux (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2019-07-23 01:47:53 |
Yoshi Kadokawa |
bug |
|
|
added subscriber Yoshi Kadokawa |
| 2019-07-23 06:21:25 |
Khaled El Mously |
linux (Ubuntu Disco): status |
In Progress |
Fix Committed |
|
| 2019-07-25 16:05:05 |
Ubuntu Kernel Bot |
tags |
cpe-onsite |
cpe-onsite verification-needed-disco |
|
| 2019-07-25 18:32:07 |
Ubuntu Kernel Bot |
tags |
cpe-onsite verification-needed-disco |
cpe-onsite verification-needed-bionic verification-needed-disco |
|
| 2019-07-31 17:24:34 |
Mauricio Faria de Oliveira |
tags |
cpe-onsite verification-needed-bionic verification-needed-disco |
cpe-onsite verification-done-disco verification-needed-bionic |
|
| 2019-07-31 18:19:01 |
Mauricio Faria de Oliveira |
tags |
cpe-onsite verification-done-disco verification-needed-bionic |
cpe-onsite verification-done-bionic verification-done-disco |
|
| 2019-08-07 08:34:20 |
Ubuntu Kernel Bot |
tags |
cpe-onsite verification-done-bionic verification-done-disco |
cpe-onsite verification-done-bionic verification-done-disco verification-needed-xenial |
|
| 2019-08-09 11:38:28 |
Launchpad Janitor |
linux (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
| 2019-08-09 11:38:28 |
Launchpad Janitor |
cve linked |
|
2019-12614 |
|
| 2019-08-09 11:38:28 |
Launchpad Janitor |
cve linked |
|
2019-13648 |
|
| 2019-08-13 08:59:53 |
Launchpad Janitor |
linux (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
| 2019-08-13 08:59:53 |
Launchpad Janitor |
cve linked |
|
2019-1125 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2000-1134 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2007-3852 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2008-0525 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2009-0416 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2011-4834 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2015-1838 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2015-7442 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2016-7489 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2018-5383 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2019-10126 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2019-12818 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2019-12819 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2019-12984 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2019-13233 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2019-13272 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2019-2101 |
|
| 2019-08-13 11:27:47 |
Launchpad Janitor |
cve linked |
|
2019-3846 |
|
| 2023-11-07 13:11:22 |
Mauricio Faria de Oliveira |
attachment added |
|
dm_fake_dev.sh https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5716855/+files/dm_fake_dev.sh |
|
