[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aRWio5wmbVX21IFu@duo.ucw.cz>
Date: Thu, 13 Nov 2025 10:19:31 +0100
From: Pavel Machek <pavel@...x.de>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
austinchang@...ology.com, fdmanana@...e.com, dsterba@...e.com
Cc: stable@...r.kernel.org, patches@...ts.linux.dev,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
patches@...nelci.org, lkft-triage@...ts.linaro.org,
jonathanh@...dia.com, f.fainelli@...il.com,
sudipm.mukherjee@...il.com, rwarsow@....de, conor@...nel.org,
hargar@...rosoft.com, broonie@...nel.org, achill@...ill.org,
sr@...dewatkins.com
Subject: [btrfs] Re: [PATCH 6.12 000/562] 6.12.58-rc2 review
Hi!
> This is the start of the stable review cycle for the 6.12.58 release.
> There are 562 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.
> austinchang <austinchang@...ology.com>
> btrfs: mark dirty extent range for out of bound prealloc extents
And someone should check this one too. It references these commits:
This is reproducible since commit 41a2ee75aab0 ("btrfs: introduce
per-inode file extent tree"), then became hidden since commit 3d7db6e8bd22
("btrfs: don't allocate file extent tree for non regular files") and then
visible again after commit 8679d2687c35 ("btrfs: initialize
inode::file_extent_tree after i_mode has been set"), which fixes the
previous commit.
But only first two are in 6.12.x, afaict.
Best regards,
Pavel
--
In cooperation with DENX Software Engineering GmbH, HRB 165235 Munich,
Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)
Powered by blists - more mailing lists