linux-kernel - Re: [PATCH v9 15/15] xfs: allow sysadmins to specify a maximum atomic write limit at mount time

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250429143847.GC25655@frogsfrogsfrogs>
Date: Tue, 29 Apr 2025 07:38:47 -0700
From: "Darrick J. Wong" <djwong@...nel.org>
To: Christoph Hellwig <hch@....de>
Cc: John Garry <john.g.garry@...cle.com>, brauner@...nel.org,
	viro@...iv.linux.org.uk, jack@...e.cz, cem@...nel.org,
	linux-fsdevel@...r.kernel.org, dchinner@...hat.com,
	linux-xfs@...r.kernel.org, linux-kernel@...r.kernel.org,
	ojaswin@...ux.ibm.com, ritesh.list@...il.com,
	martin.petersen@...cle.com, linux-ext4@...r.kernel.org,
	linux-block@...r.kernel.org, catherine.hoang@...cle.com,
	linux-api@...r.kernel.org
Subject: Re: [PATCH v9 15/15] xfs: allow sysadmins to specify a maximum
 atomic write limit at mount time

On Tue, Apr 29, 2025 at 02:22:11PM +0200, Christoph Hellwig wrote:
> So I guess the property variant didn't work out based on the replies
> from Darrick last round?

Correct.  Calling setxattr on the property wouldn't call
xfs_set_max_atomic_write_opt to change the operational limit, and I
don't want to start up the whole magic xattrs discussion again by making
xfs_xattr_set do extra things if name=="trusted.xfs:max_atomic_write".

(Though iirc you were the most opposed to magic xattrs, and my
opposition is 45% yuck factor and 55% "hch will nak it anyway" ;) )

--D