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

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

Message-ID: <EF15582A-A753-46F0-8011-E4EBFAFB33C7@hammerspace.com>
Date: Thu, 04 Dec 2025 12:36:31 -0500
From: Benjamin Coddington <bcodding@...merspace.com>
To: Chuck Lever <chuck.lever@...cle.com>
Cc: Alexander Viro <viro@...iv.linux.org.uk>,
 Christian Brauner <brauner@...nel.org>, 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 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 assume that since you sent To: Al/Christian, they would be taking this
> through one of the VFS trees; hence my R-b.

Thanks for that - usually there's some discussion on which tree would take
this which I didn't see yet.  Hope Al/Christian will pick it up.

> If you're going only for linux-next, you can open your own kernel.org
> account and set up a git repo there, then Stephen can pull from that
> repo into linux-next and fs-next.

I do need to get that done.

Ben