linux-ext4 - [PATCH v2 0/1] xfs/539: Ignore remount failures on v5 xfs

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <cover.1741094926.git.nirjhar.roy.lists@gmail.com>
Date: Tue,  4 Mar 2025 13:48:15 +0000
From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@...il.com>
To: fstests@...r.kernel.org
Cc: linux-ext4@...r.kernel.org,
	linux-xfs@...r.kernel.org,
	ritesh.list@...il.com,
	ojaswin@...ux.ibm.com,
	djwong@...nel.org,
	zlang@...nel.org,
	david@...morbit.com,
	nirjhar.roy.lists@...il.com
Subject: [PATCH v2 0/1] xfs/539: Ignore remount failures on v5 xfs

The test just checks for the deprecation dmesg
warnings when remounted with noattr2 and ikeep, and they appear even if the
remount fails. I wrote the patch because xfs/539 has started failing in one of
our fstests CI runs because RHEL 10 has started disabling xfs v4 support i.e,
CONFIG_XFS_SUPPORT_V4=n. The reason why it was not failing with CONFIG_XFS_SUPPORT_V4=y
is because remount was incorrectly succeeding - reason is explained in [2].

[v1] --> v2
 - Removed patch 2/3 and patch 3/3 for now,
 - For patch 1/3 - Ignore the mount failure instead of skipping noattr2.

[v1] https://lore.kernel.org/all/cover.1739363803.git.nirjhar.roy.lists@gmail.com/
[2] https://lore.kernel.org/all/Z65o6nWxT00MaUrW@dread.disaster.area/

Nirjhar Roy (IBM) (1):
  xfs/539: Ignore remount failures on v5 xfs

 tests/xfs/539 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--
2.34.1