| Date | Wed, 20 Mar 2024 18:12:46 -0400 | From | Sasha Levin <> | Subject | Re: btrfs fix missing in 5.10-stable was Re: [PATCH 5.10 00/73] 5.10.213-rc1 review |
| |
On Wed, Mar 20, 2024 at 02:44:06PM +0100, Pavel Machek wrote: >Hi! > >> This is the start of the stable review cycle for the 5.10.213 release. >> There are 73 patches in this series, all will be posted as a response >> to this one. If anyone has any issues with these being applied, please >> let me know. > >While debugging "search for known-bad commit" script, I noticed: > >We have > >41b3cc57d626d c2e39305299f0 btrfs: clear extent buffer uptodate when >we fail to write it > >commit in 5.10, which is fixed by this, but we don't have that one: > >651740a502411 btrfs: check WRITE_ERR when trying to read an extent >buffer
Hey Pavel,
There are two reasons it didn't make it into 5.10 or 5.4:
1. It doesn't build on any of those kernels, and we haven't gotten a backport we could apply.
2. There's a follow-up fix that happened soon after ( 40cdc509877b ("btrfs: skip reserved bytes warning on unmount after log cleanup failure") ) which needs a backport on it's own.
-- Thanks, Sasha
|