This bug was fixed in the package linux - 5.8.0-53.60
---
linux (5.8.0-53.60) groovy; urgency=medium
* CVE-2021-3491
- io_uring: fix provide_buffers sign extension
- io_uring: fix overflows checks in provide buffers
- SAUCE: proc: Avoid mixing integer types in mem_rw()
This bug was fixed in the package linux - 5.4.0-73.82
---
linux (5.4.0-73.82) focal; urgency=medium
* focal/linux: 5.4.0-73.82 -proposed tracker (LP: #1923781)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CIFS DFS entries not accessible with
This bug was fixed in the package linux - 4.15.0-143.147
---
linux (4.15.0-143.147) bionic; urgency=medium
* bionic/linux: 4.15.0-143.147 -proposed tracker (LP: #1923811)
* CVE-2021-29650
- netfilter: x_tables: Use correct memory barriers.
* LRMv4: switch to signing
I used the same steps to verify it and can confirm it's succeeded in
bionic-proposed too
fio --name=test1 --filename /dev/bcache0 --direct 1 --rw=randrw
--bs=32k,4k --ioengine=libaio --iodepth=1
Then I monitoring the cache_available_percent and writeback rate.
I no longer see the
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900438
Title:
Bcache bypasse writeback on caching device with fragmentation
To manage notifications about
I used the same steps to verify it and can conconfirm it's succeeded
fio --name=test1 --filename /dev/bcache0 --direct 1 --rw=randrw
--bs=32k,4k --ioengine=libaio --iodepth=1
Then I monitoring the cache_available_percent and writeback rate.
I no longer see the cache_available_percent dropped to
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-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag
I've done the verification of the focal-proposed kernel.
I used below fio command to cause the bcache fragmentation:
fio --name=test1 --filename /dev/bcache0 --direct 1 --rw=randrw
--bs=32k,4k --ioengine=libaio --iodepth=1
Then I monitoring the cache_available_percent and writeback rate.
I no
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
This bug was fixed in the package linux - 5.11.0-14.15
---
linux (5.11.0-14.15) hirsute; urgency=medium
* hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)
* Packaging resync (LP: #1786013)
- update dkms package versions
* Include Infiniband Peer Memory
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
You received this bug notification because you
** Changed in: linux (Ubuntu Bionic)
Importance: Medium => High
** Changed in: linux (Ubuntu Focal)
Importance: Medium => High
** Changed in: linux (Ubuntu Groovy)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Assignee: dongdong tao (taodd)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900438
Title:
Bcache
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) =>
** Description changed:
SRU Justification:
[Impact]
- This bug in bcache [insert correct area] affects I/O performance on all
versions of the kernel [correct versions affected]. It is particularly negative
on ceph if used with bcache.
+ This bug in bcache affects I/O performance on all
** Description changed:
- Hello,
+ SRU Justification:
- An upstream bug has been opened on the matter for quite some time now [0].
- I can reproduce easily on our production compute node instance, which are
trusty host with xenial hwe kernels (4.15.0-101-generic).
- However due to heavy
Here is the latest updated patch and the progress being made in upstream
https://marc.info/?l=linux-bcache=160981605206306=1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900438
Title:
Bcache
I've just submitted a patch[1] to upstream for review to help with this problem.
The key is to speed up the writeback rate when the fragmentation is high.
Here are the comments from the patch:
Current way to calculate the writeback rate only considered the
dirty sectors, this usually works fine
I tried to run the apport-collect on one of the server we can see the
issue on :
Waiting to hear from Launchpad about your decision...
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
** 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/1900438
Title:
Bcache bypasse writeback on caching device with fragmentation
To
20 matches
Mail list logo
