On Wed, 9 Oct 2024 at 08:22, Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote: > > On Tue, 8 Oct 2024 at 17:42, Greg Kroah-Hartman > <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > This is the start of the stable review cycle for the 6.10.14 release. > > There are 482 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. > > > > Responses should be made by Thu, 10 Oct 2024 11:55:15 +0000. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.10.14-rc1.gz > > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.10.y > > and the diffstat can be found below. > > > > thanks, > > > > greg k-h > > > The LTP syscalls fanotify22 test failed (broken). > This regression is noticed on linux.6.10.y, linux.6.11.y and linux.6.6.y. > > We are bisecting this issue. The bisection pointed to patch b1a855f8a4fd ("ext4: don't set SB_RDONLY after filesystem errors") [ Upstream commit d3476f3dad4ad68ae5f6b008ea6591d1520da5d8 ] Reverting patch b1a855f8a4fd ("ext4: don't set SB_RDONLY after filesystem errors") makes ltp-syscalls/fanotify22 pass. That said, I also checked Linus tree and fanotify22 fails there too. Reverting the upstream patch d3476f3dad4a ("ext4: don't set SB_RDONLY after filesystem errors") from Linux tree v6.12-rc2-58-g75b607fab38d and run syscalls/fanotify22 it pass. Any ideas whats wrong here? Cheers, Anders
