linux-kernel - Re: [PATCH v4 0/3] Allow knfsd to use atomic

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

Message-ID: <20251205-drucken-stutzen-bc27967b943b@brauner>
Date: Fri, 5 Dec 2025 10:31:44 +0100
From: Christian Brauner <brauner@...nel.org>
To: Benjamin Coddington <bcodding@...merspace.com>
Cc: Chuck Lever <chuck.lever@...cle.com>, 
	Alexander Viro <viro@...iv.linux.org.uk>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, 
	linux-nfs@...r.kernel.org
Subject: Re: [PATCH v4 0/3] Allow knfsd to use atomic_open()

On Thu, Dec 04, 2025 at 12:36:31PM -0500, Benjamin Coddington wrote:
> On 4 Dec 2025, at 12:33, Chuck Lever wrote:
> 
> > On 12/4/25 10:05 AM, Benjamin Coddington wrote:
> >> Hi Chuck, Christian, Al,
> >>
> >> Comments have died down.  I have some review on this one, and quite a lot of
> >> testing in-house.  What else can I do to get this into linux-next on this
> >> cycle?
> > The merge window is open right now, so any new work like this will be
> > targeted for the next kernel, not v6.19-rc.
> 
> Yes indeed, too late for v6.19.

I've taken it into vfs-6.20.atomic_open and rebased this onto current
master and will do a final rebase after -rc1. Let me know if I messed
something up. Thanks for pinging.