linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>,
	Calum Mackay <calum.mackay@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH pynfs 0/7] nfs4.1: add some basic directory delegation tests
Date: Tue, 30 Sep 2025 09:57:06 -0400	[thread overview]
Message-ID: <8aa00b92ac061ca233bd016b426725170ac55e6b.camel@kernel.org> (raw)
In-Reply-To: <b85d61ab-4df9-4b99-b998-399d0dfd9b69@oracle.com>

On Tue, 2025-09-30 at 09:48 -0400, Chuck Lever wrote:
> On 9/30/25 7:37 AM, Jeff Layton wrote:
> > Add basic support for testing both GET_DIR_DELEGATION operations and
> > CB_NOTIFY.
> > 
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > ---
> > Jeff Layton (7):
> >       nfs4.1: add proposed NOTIFY4_GFLAG_EXTEND flag
> >       pynfs: add a getfh() to the end of create_obj() compound
> >       server41tests: add a basic GET_DIR_DELEGATION test
> >       server41tests: add a test for duplicate GET_DIR_DELEGATION requests
> >       server41tests: add a test for removal from dir with dir delegation
> >       server41tests: add a test for diretory add notifications
> >       server41tests: add test for rename event notifications
> > 
> >  nfs4.1/nfs4client.py                 |   6 +
> >  nfs4.1/server41tests/__init__.py     |   1 +
> >  nfs4.1/server41tests/environment.py  |   2 +-
> >  nfs4.1/server41tests/st_dir_deleg.py | 221 +++++++++++++++++++++++++++++++++++
> >  nfs4.1/xdrdef/nfs4.x                 |   3 +-
> >  5 files changed, 231 insertions(+), 2 deletions(-)
> > ---
> > base-commit: 3c14d9e3ad12272ab2f6092c85bb28ab03951484
> > change-id: 20250930-dir-deleg-4ae7364fb398
> > 
> > Best regards,
> 
> Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
> 
> But one question: should these new tests not be in the "all" group?
> Seems like most NFS server implementations won't support directory
> delegations.
> 

I had meant to remove that group before posting and then forgot about
it. That is a good point though...

Ideally what would best would be to try and run it, and just make it a
non-fatal error if the initial GET_DIR_DELEGATION fails? Maybe just
make it pass_warn() in that case?

I like that idea better than hiding this away where we forget to run
it. I'll see what I can put together.

Thanks,
-- 
Jeff Layton <jlayton@kernel.org>

      reply	other threads:[~2025-09-30 13:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 11:37 [PATCH pynfs 0/7] nfs4.1: add some basic directory delegation tests Jeff Layton
2025-09-30 11:37 ` [PATCH pynfs 1/7] nfs4.1: add proposed NOTIFY4_GFLAG_EXTEND flag Jeff Layton
2025-09-30 11:37 ` [PATCH pynfs 2/7] pynfs: add a getfh() to the end of create_obj() compound Jeff Layton
2025-09-30 11:37 ` [PATCH pynfs 3/7] server41tests: add a basic GET_DIR_DELEGATION test Jeff Layton
2025-09-30 11:37 ` [PATCH pynfs 4/7] server41tests: add a test for duplicate GET_DIR_DELEGATION requests Jeff Layton
2025-09-30 11:37 ` [PATCH pynfs 5/7] server41tests: add a test for removal from dir with dir delegation Jeff Layton
2025-09-30 11:37 ` [PATCH pynfs 6/7] server41tests: add a test for diretory add notifications Jeff Layton
2025-09-30 11:37 ` [PATCH pynfs 7/7] server41tests: add test for rename event notifications Jeff Layton
2025-09-30 13:48 ` [PATCH pynfs 0/7] nfs4.1: add some basic directory delegation tests Chuck Lever
2025-09-30 13:57   ` Jeff Layton [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=8aa00b92ac061ca233bd016b426725170ac55e6b.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=calum.mackay@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).