linux-ext4 - [PATCH 5.15 0/2] fix LTP regression in fanotify22

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250617210956.146158-1-amir73il@gmail.com>
Date: Tue, 17 Jun 2025 23:09:54 +0200
From: Amir Goldstein <amir73il@...il.com>
To: Jan Kara <jack@...e.cz>
Cc: Theodore Ts'o <tytso@....edu>,
	Sasha Levin <sashal@...nel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-ext4@...r.kernel.org,
	ltp@...r.kernel.org,
	stable@...r.kernel.org
Subject: [PATCH 5.15 0/2] fix LTP regression in fanotify22

Jan,

I noticed that fanotify22, the FAN_FS_ERROR test has regressed in the
5.15.y stable tree.

This is because commit d3476f3dad4a ("ext4: don't set SB_RDONLY after
filesystem errors") was backported to 5.15.y and the later Fixes
commit could not be cleanly applied to 5.15.y over the new mount api
re-factoring.

I am not sure it is critical to fix this regression, because it is
mostly a regression in a test feature, but I think the backport is
pretty simple, although I could be missing something.

Please ACK if you agree that this backport should be applied to 5.15.y.

Thanks,
Amir.

Amir Goldstein (2):
  ext4: make 'abort' mount option handling standard
  ext4: avoid remount errors with 'abort' mount option

 fs/ext4/ext4.h  |  1 +
 fs/ext4/super.c | 15 +++++++++------
 2 files changed, 10 insertions(+), 6 deletions(-)

-- 
2.47.1