linux-kernel - Re: re-enable IOCB_NOWAIT writes to files v2

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: <20251125-loten-fabuliert-c0fb6b195b53@brauner>
Date: Tue, 25 Nov 2025 10:18:32 +0100
From: Christian Brauner <brauner@...nel.org>
To: Christoph Hellwig <hch@....de>
Cc: Al Viro <viro@...iv.linux.org.uk>, David Sterba <dsterba@...e.com>, 
	Jan Kara <jack@...e.cz>, Mike Marshall <hubcap@...ibond.com>, 
	Martin Brandenburg <martin@...ibond.com>, Carlos Maiolino <cem@...nel.org>, Stefan Roesch <shr@...com>, 
	Jeff Layton <jlayton@...nel.org>, linux-kernel@...r.kernel.org, linux-btrfs@...r.kernel.org, 
	linux-fsdevel@...r.kernel.org, gfs2@...ts.linux.dev, io-uring@...r.kernel.org, 
	devel@...ts.orangefs.org, linux-unionfs@...r.kernel.org, linux-mtd@...ts.infradead.org, 
	linux-xfs@...r.kernel.org, linux-nfs@...r.kernel.org
Subject: Re: re-enable IOCB_NOWAIT writes to files v2

On Thu, Nov 20, 2025 at 07:47:21AM +0100, Christoph Hellwig wrote:
> Hi all,
> 
> commit 66fa3cedf16a ("fs: Add async write file modification handling.")
> effectively disabled IOCB_NOWAIT writes as timestamp updates currently
> always require blocking, and the modern timestamp resolution means we
> always update timestamps.  This leads to a lot of context switches from
> applications using io_uring to submit file writes, making it often worse
> than using the legacy aio code that is not using IOCB_NOWAIT.
> 
> This series allows non-blocking updates for lazytime if the file system
> supports it, and adds that support for XFS.
> 
> It also fixes the layering bypass in btrfs when updating timestamps on
> device files for devices removed from btrfs usage, and FMODE_NOCMTIME
> handling in the VFS now that nfsd started using it.  Note that I'm still
> not sure that nfsd usage is fully correct for all file systems, as only
> XFS explicitly supports FMODE_NOCMTIME, but at least the generic code
> does the right thing now.

It's a bit too close to the merge window for my taste and we have about
17 pull request topics for this cycle already.

So I'll take this for vfs-6.20.iomap. As usual I'll create that branch
now so that the patches don't get lost and will rebase once v6.19-rc1 is
out.