linux-kernel - Re: [GIT PULL 16/17 for v6.19] vfs fd prepare

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

Message-ID: <20251201141556.GG3538@ZenIV>
Date: Mon, 1 Dec 2025 14:15:56 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: Christian Brauner <brauner@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL 16/17 for v6.19] vfs fd prepare

On Fri, Nov 28, 2025 at 05:48:27PM +0100, Christian Brauner wrote:
> Hey Linus,
> 
> /* Summary */
> Note: This work came late in the cycle but the series is quite nice and
> worth doing. It removes roughly double the code that it adds and
> eliminates a lot of convoluted cleanup logic across the kernel.
> 
> An alternative pull request (vfs-6.19-rc1.fd_prepare.fs) is available
> that contains only the more simple filesystem-focused conversions in
> case you'd like to pull something more conservative.
> 
> Note this branch also contains two reverts for the KVM FD_PREPARE()
> conversions as the KVM maintainers have indicated they would like to
> take those changes through the KVM tree in the next cycle. Also gets rid
> of a merge conflict. I chose a revert to not rebase the branch
> unnecessarily so close to the merge window.

Frankly, that hadn't gotten anywhere near enough exposure in -next and
it's far too large and invasive.  The same lack of exposure goes for
the alternative branch.