From: "Chuck Lever" <cel@kernel.org>
To: "Christian Brauner" <brauner@kernel.org>,
"Jeff Layton" <jlayton@kernel.org>,
"Chuck Lever" <chuck.lever@oracle.com>
Cc: "Alexander Viro" <viro@zeniv.linux.org.uk>,
"Jan Kara" <jack@suse.cz>,
"Alexander Aring" <alex.aring@gmail.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
NeilBrown <neil@brown.name>,
"Olga Kornievskaia" <okorniev@redhat.com>,
"Dai Ngo" <Dai.Ngo@oracle.com>, "Tom Talpey" <tom@talpey.com>,
"Trond Myklebust" <trondmy@kernel.org>,
"Anna Schumaker" <anna@kernel.org>,
"Amir Goldstein" <amir73il@gmail.com>,
"Calum Mackay" <calum.mackay@oracle.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-nfs@vger.kernel.org
Subject: Re: (subset) [PATCH v3 00/28] vfs/nfsd: add support for CB_NOTIFY callbacks in directory delegations
Date: Mon, 18 May 2026 12:05:01 -0400 [thread overview]
Message-ID: <b727a784-1c7c-41dd-83a8-a43084e4c4f9@app.fastmail.com> (raw)
In-Reply-To: <20260515-weltschmerz-folgen-68ca0db1ef84@brauner>
On Fri, May 15, 2026, at 1:26 PM, Christian Brauner wrote:
> On Tue, 28 Apr 2026 08:09:44 +0100, Jeff Layton wrote:
>> Re-posting the set per Christian's request. The only difference in this
>> version is a small error handling fix in alloc_init_dir_deleg(). The old
>> version could crash since release_pages() can't handle an array with
>> NULL pointers in it.
>>
>> ---------------------------------8<------------------------------------
>>
>> [...]
>
> @Chuck, @Jeff, I've only merged the vfs specific changes into a stable branch.
> You can pull it I won't touch it again. You can pull the nfsd work in in
> whatever form you like. Same procedure I use with io_uring et al.
>
> Let me know if that work for you.
>
> ---
>
> Applied to the vfs-7.2.directory.delegations branch of the vfs/vfs.git
> tree.
> Patches in the vfs-7.2.directory.delegations branch should appear in
> linux-next soon.
>
> Please report any outstanding bugs that were missed during review in a
> new review to the original patch series allowing us to drop it.
>
> It's encouraged to provide Acked-bys and Reviewed-bys even though the
> patch has now been applied. If possible patch trailers will be updated.
>
> Note that commit hashes shown below are subject to change due to rebase,
> trailer updates or similar. If in doubt, please check the listed branch.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
> branch: vfs-7.2.directory.delegations
>
> [01/28] filelock: pass current blocking lease to
> trace_break_lease_block() rather than "new_fl"
> https://git.kernel.org/vfs/vfs/c/89330d3a60f7
> [02/28] filelock: add support for ignoring deleg breaks for dir change
> events
> https://git.kernel.org/vfs/vfs/c/24cbf43337f4
> [03/28] filelock: add a tracepoint to start of break_lease()
> https://git.kernel.org/vfs/vfs/c/e39026a86b48
> [04/28] filelock: add an inode_lease_ignore_mask helper
> https://git.kernel.org/vfs/vfs/c/95825fdcc0b0
> [05/28] fsnotify: new tracepoint in fsnotify()
> https://git.kernel.org/vfs/vfs/c/ad4489dcd08d
> [06/28] fsnotify: add fsnotify_modify_mark_mask()
> https://git.kernel.org/vfs/vfs/c/12ffbb117b64
> [07/28] fsnotify: add FSNOTIFY_EVENT_RENAME data type
> https://git.kernel.org/vfs/vfs/c/010043003c0c
Looks good.
To make the NFSD pieces apply, I need v7.1-rc4 and
vfs-7.2.directory.delegations merged into vfs.all. Given your
regular merge cadence over the past few weeks, I expect that
will happen end of this week? Early next?
--
Chuck Lever
prev parent reply other threads:[~2026-05-18 16:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 7:09 Jeff Layton
2026-04-28 7:09 ` [PATCH v3 01/28] filelock: pass current blocking lease to trace_break_lease_block() rather than "new_fl" Jeff Layton
2026-04-28 7:09 ` [PATCH v3 02/28] filelock: add support for ignoring deleg breaks for dir change events Jeff Layton
2026-04-28 7:09 ` [PATCH v3 03/28] filelock: add a tracepoint to start of break_lease() Jeff Layton
2026-04-28 7:09 ` [PATCH v3 04/28] filelock: add an inode_lease_ignore_mask helper Jeff Layton
2026-04-28 7:09 ` [PATCH v3 05/28] fsnotify: new tracepoint in fsnotify() Jeff Layton
2026-04-28 7:09 ` [PATCH v3 06/28] fsnotify: add fsnotify_modify_mark_mask() Jeff Layton
2026-04-28 7:09 ` [PATCH v3 07/28] fsnotify: add FSNOTIFY_EVENT_RENAME data type Jeff Layton
2026-04-28 7:09 ` [PATCH v3 08/28] nfsd: check fl_lmops in nfsd_breaker_owns_lease() Jeff Layton
2026-04-28 7:09 ` [PATCH v3 09/28] nfsd: add protocol support for CB_NOTIFY Jeff Layton
2026-04-28 7:09 ` [PATCH v3 10/28] nfs_common: add new NOTIFY4_* flags proposed in RFC8881bis Jeff Layton
2026-04-28 7:09 ` [PATCH v3 11/28] nfsd: allow nfsd to get a dir lease with an ignore mask Jeff Layton
2026-04-28 7:09 ` [PATCH v3 12/28] nfsd: update the fsnotify mark when setting or removing a dir delegation Jeff Layton
2026-04-28 7:09 ` [PATCH v3 13/28] nfsd: make nfsd4_callback_ops->prepare operation bool return Jeff Layton
2026-04-28 7:09 ` [PATCH v3 14/28] nfsd: add callback encoding and decoding linkages for CB_NOTIFY Jeff Layton
2026-04-28 7:09 ` [PATCH v3 15/28] nfsd: use RCU to protect fi_deleg_file Jeff Layton
2026-04-28 7:10 ` [PATCH v3 16/28] nfsd: add data structures for handling CB_NOTIFY Jeff Layton
2026-04-28 7:10 ` [PATCH v3 17/28] nfsd: add notification handlers for dir events Jeff Layton
2026-04-28 7:10 ` [PATCH v3 18/28] nfsd: add tracepoint to dir_event handler Jeff Layton
2026-04-28 7:10 ` [PATCH v3 19/28] nfsd: apply the notify mask to the delegation when requested Jeff Layton
2026-04-28 7:10 ` [PATCH v3 20/28] nfsd: add helper to marshal a fattr4 from completed args Jeff Layton
2026-04-28 7:10 ` [PATCH v3 21/28] nfsd: allow nfsd4_encode_fattr4_change() to work with no export Jeff Layton
2026-04-28 7:10 ` [PATCH v3 22/28] nfsd: send basic file attributes in CB_NOTIFY Jeff Layton
2026-04-28 7:10 ` [PATCH v3 23/28] nfsd: allow encoding a filehandle into fattr4 without a svc_fh Jeff Layton
2026-04-28 7:10 ` [PATCH v3 24/28] nfsd: add a fi_connectable flag to struct nfs4_file Jeff Layton
2026-04-28 7:10 ` [PATCH v3 25/28] nfsd: add the filehandle to returned attributes in CB_NOTIFY Jeff Layton
2026-04-28 7:10 ` [PATCH v3 26/28] nfsd: properly track requested child attributes Jeff Layton
2026-04-28 7:10 ` [PATCH v3 27/28] nfsd: track requested dir attributes Jeff Layton
2026-04-28 7:10 ` [PATCH v3 28/28] nfsd: add support to CB_NOTIFY for dir attribute changes Jeff Layton
2026-04-29 13:41 ` [PATCH v3 00/28] vfs/nfsd: add support for CB_NOTIFY callbacks in directory delegations Chuck Lever
2026-05-15 17:26 ` (subset) " Christian Brauner
2026-05-18 16:05 ` Chuck Lever [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b727a784-1c7c-41dd-83a8-a43084e4c4f9@app.fastmail.com \
--to=cel@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=alex.aring@gmail.com \
--cc=amir73il@gmail.com \
--cc=anna@kernel.org \
--cc=brauner@kernel.org \
--cc=calum.mackay@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=corbet@lwn.net \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=tom@talpey.com \
--cc=trondmy@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®