Linux Documentation
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>,
	Chuck Lever <chuck.lever@oracle.com>,
	 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>
Cc: Alexander Aring <alex.aring@gmail.com>,
	Amir Goldstein <amir73il@gmail.com>,  Jan Kara <jack@suse.cz>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner	 <brauner@kernel.org>,
	Calum Mackay <calum.mackay@oracle.com>,
		linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
		linux-nfs@vger.kernel.org
Subject: Re: [PATCH v4 03/21] nfs_common: add new NOTIFY4_* flags proposed in RFC8881bis
Date: Mon, 08 Jun 2026 12:37:59 -0400	[thread overview]
Message-ID: <906ff2a1fa578558954b82941ce0809c4257e443.camel@kernel.org> (raw)
In-Reply-To: <bf852bf8-2d80-4b12-8d7c-bb0770c8b379@app.fastmail.com>

On Mon, 2026-06-08 at 12:23 -0400, Chuck Lever wrote:
> Unfortunately, reviewing this series slipped off my radar. I'm just now
> getting to it. I'm going to do this in order and some of the earlier
> reviews are cosmetic. But there are some significant changes needed
> later on, so I expect we'll need to redrive this series and punt it to
> v7.3.
> 

That's reasonable. We had some unrelated new bugs crop up near the end
of the cycle that made it hard to get this in and tested properly. I'd
like to propose that we keep the VFS bits

> One thing you might update before you repost is to remove the "Acked-by:
> Chuck Lever" throughout the series.
> 

Ok. I think b4 added that.

> 
> Nit: the Subject: prefix should be "nfsd:" not "nfs_common:"
> 

include/linux/sunrpc/xdrgen/nfs4_1.h is a shared header. Anna will
presumably need this patch as well.

> 
> On Fri, May 22, 2026, at 8:28 AM, Jeff Layton wrote:
> > RFC8881bis adds some new flags to GET_DIR_DELEGATION that we very much
> > need to support.
> 
> Nit: Let's say: "RFC8881bis adds new flags to GET_DIR_DELEGATION
> that later patches consume."
> 
> One recent private comment to me was a question about whether we can
> trust the stability of the specification, which is still a WG document
> and has been for years. This patch's commit message should address
> that.
> 

That's definitely an open question. We are definitely adopting these
changes before the ink is dry. We might have to modify things later,
especially once there is more client-side experience.

I'm open to verbiage suggestions here.


> 
> > diff --git a/Documentation/sunrpc/xdr/nfs4_1.x 
> > b/Documentation/sunrpc/xdr/nfs4_1.x
> > index 632f5b579c39..aa14b590b524 100644
> > --- a/Documentation/sunrpc/xdr/nfs4_1.x
> > +++ b/Documentation/sunrpc/xdr/nfs4_1.x
> > @@ -416,7 +416,21 @@ enum notify_type4 {
> >          NOTIFY4_REMOVE_ENTRY = 2,
> >          NOTIFY4_ADD_ENTRY = 3,
> >          NOTIFY4_RENAME_ENTRY = 4,
> > -        NOTIFY4_CHANGE_COOKIE_VERIFIER = 5
> > +        NOTIFY4_CHANGE_COOKIE_VERIFIER = 5,
> > +        /*
> > +         * Added in NFSv4.1 bis document
> > +         */
> 
> I clarified this comment: "/* Proposed in RFC8881bis */"
> 
> I rebuilt the generated source to confirm that it hasn't been altered
> by recent changes to xdrgen or this comment change. The only thing
> that changed in the output was the header's timestamp.
> 

Sounds good.
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2026-06-08 16:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22 12:28 [PATCH v4 00/21] nfsd: add support for CB_NOTIFY callbacks in directory delegations Jeff Layton
2026-05-22 12:28 ` [PATCH v4 01/21] nfsd: check fl_lmops in nfsd_breaker_owns_lease() Jeff Layton
2026-05-22 12:28 ` [PATCH v4 02/21] nfsd: add protocol support for CB_NOTIFY Jeff Layton
2026-05-22 12:28 ` [PATCH v4 03/21] nfs_common: add new NOTIFY4_* flags proposed in RFC8881bis Jeff Layton
2026-06-08 16:23   ` Chuck Lever
2026-06-08 16:37     ` Jeff Layton [this message]
2026-05-22 12:28 ` [PATCH v4 04/21] nfsd: allow nfsd to get a dir lease with an ignore mask Jeff Layton
2026-05-22 12:28 ` [PATCH v4 05/21] nfsd: update the fsnotify mark when setting or removing a dir delegation Jeff Layton
2026-05-22 12:28 ` [PATCH v4 06/21] nfsd: make nfsd4_callback_ops->prepare operation bool return Jeff Layton
2026-05-22 12:28 ` [PATCH v4 07/21] nfsd: add callback encoding and decoding linkages for CB_NOTIFY Jeff Layton
2026-05-22 12:28 ` [PATCH v4 08/21] nfsd: use RCU to protect fi_deleg_file Jeff Layton
2026-05-22 12:28 ` [PATCH v4 09/21] nfsd: add data structures for handling CB_NOTIFY Jeff Layton
2026-05-22 12:28 ` [PATCH v4 10/21] nfsd: add notification handlers for dir events Jeff Layton
2026-05-22 12:29 ` [PATCH v4 11/21] nfsd: add tracepoint to dir_event handler Jeff Layton
2026-05-22 14:31   ` Steven Rostedt
2026-05-22 14:37     ` Jeff Layton
2026-05-22 12:29 ` [PATCH v4 12/21] nfsd: apply the notify mask to the delegation when requested Jeff Layton
2026-05-22 12:29 ` [PATCH v4 13/21] nfsd: add helper to marshal a fattr4 from completed args Jeff Layton
2026-05-22 12:29 ` [PATCH v4 14/21] nfsd: allow nfsd4_encode_fattr4_change() to work with no export Jeff Layton
2026-05-22 12:29 ` [PATCH v4 15/21] nfsd: send basic file attributes in CB_NOTIFY Jeff Layton
2026-05-22 12:29 ` [PATCH v4 16/21] nfsd: allow encoding a filehandle into fattr4 without a svc_fh Jeff Layton
2026-05-22 12:29 ` [PATCH v4 17/21] nfsd: add a fi_connectable flag to struct nfs4_file Jeff Layton
2026-05-22 12:29 ` [PATCH v4 18/21] nfsd: add the filehandle to returned attributes in CB_NOTIFY Jeff Layton
2026-05-22 12:29 ` [PATCH v4 19/21] nfsd: properly track requested child attributes Jeff Layton
2026-05-22 12:29 ` [PATCH v4 20/21] nfsd: track requested dir attributes Jeff Layton
2026-05-22 13:24   ` Chuck Lever
2026-05-22 12:29 ` [PATCH v4 21/21] nfsd: add support to CB_NOTIFY for dir attribute changes Jeff Layton

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=906ff2a1fa578558954b82941ce0809c4257e443.camel@kernel.org \
    --to=jlayton@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=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=jack@suse.cz \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=okorniev@redhat.com \
    --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