From: Calum Mackay <calum.mackay@oracle.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: Calum Mackay <calum.mackay@oracle.com>,
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>,
Scott Mayhew <smayhew@redhat.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH pynfs v3 00/26] nfs4.1: add some directory delegation testcases
Date: Tue, 23 Jun 2026 22:33:48 +0100 [thread overview]
Message-ID: <ebb03dbb-df8c-4270-9bd1-9a2fa64b7e18@oracle.com> (raw)
In-Reply-To: <20260619-dir-deleg-v3-0-1077ce8aab1b@kernel.org>
Thanks very much Jeff,
I have a bit of a backlog, again, but will get to these asap.
cheers,
c.
On 19/06/2026 8:22 pm, Jeff Layton wrote:
> Long delay since v2, but the CB_NOTIFY patches only recently got merged
> into Chuck's nfsd-testing branch. They're currently slated to make v7.3.
> This version of the series fixes some potential state leaks that Scott
> pointed out, and adds a patch to make the output a bit less chatty with
> normal settings.
>
> Original cover letter follows:
>
> ---------------------8<-------------------
>
> This patchset adds some new testcases for directory delegations.
>
> DIRDELEG1-7 should pass on current mainline kernels, with recall-only
> support. The rest require CB_NOTIFY support. If the server doesn't
> offer notifications, then the tests pass_warn (so there should be no
> failures in those cases):
>
> https://lore.kernel.org/linux-nfs/20260416-dir-deleg-v2-0-851426a550f6@kernel.org/
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
>
> ---
> Changes in v3:
> - Ensure we clean up state after tests
> - Demote some extra-chatty messages to debug level
> - Link to v2: https://lore.kernel.org/r/20260416-dir-deleg-v2-0-fad510db5941@kernel.org
>
> Changes in v2:
> - Added more tests for CB_NOTIFY behavior
> - Link to v1: https://lore.kernel.org/r/20260407-dir-deleg-v1-0-54c998eab72b@kernel.org
>
> ---
> Jeff Layton (26):
> nfs4.1: add proposed NOTIFY4_GFLAG_EXTEND flag
> nfs4.1: 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: pass_warn() when server doesn't support dir delegations
> server41tests: test remove triggers dir delegation recall
> server41tests: test rename triggers dir delegation recall
> server41tests: test mkdir triggers dir delegation recall
> server41tests: test link triggers dir delegation recall
> server41tests: test no notifications without GFLAG_EXTEND
> server41tests: test unrequested notification type triggers recall
> server41tests: add a test for removal from dir with dir delegation
> server41tests: add a test for directory add notifications
> server41tests: add test for RENAME event notifications
> server41tests: verify child attributes in ADD notification
> server41tests: test CHANGE_DIR_ATTRS notification
> server41tests: test mkdir triggers ADD notification
> server41tests: test DELEGRETURN stops notifications
> server41tests: verify filehandle in ADD notification
> server41tests: test cross-directory rename REMOVE notification
> server41tests: test cross-directory rename ADD notification on target
> server41tests: test link triggers ADD notification
> server41tests: test same-client changes don't trigger notifications
> server41tests: test cross-directory rename-over nad_old_entry
> server41tests: test within-directory rename-over nad_old_entry
> nfs4.1: move a lot of log/log_cb.info messages to log/log_cb.debug
>
> nfs4.1/nfs4client.py | 42 +-
> nfs4.1/server41tests/__init__.py | 1 +
> nfs4.1/server41tests/environment.py | 6 +-
> nfs4.1/server41tests/st_delegation.py | 3 -
> nfs4.1/server41tests/st_dir_deleg.py | 1117 +++++++++++++++++++++++++++++++++
> nfs4.1/xdrdef/nfs4.x | 3 +-
> 6 files changed, 1147 insertions(+), 25 deletions(-)
> ---
> base-commit: cd4701827a8261fedbfb4c6e39029fb9671321a6
> change-id: 20260331-dir-deleg-a1b3475f8385
>
> Best regards,
prev parent reply other threads:[~2026-06-23 21:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 19:22 [PATCH pynfs v3 00/26] nfs4.1: add some directory delegation testcases Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 01/26] nfs4.1: add proposed NOTIFY4_GFLAG_EXTEND flag Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 02/26] nfs4.1: add a getfh() to the end of create_obj() compound Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 03/26] server41tests: add a basic GET_DIR_DELEGATION test Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 04/26] server41tests: add a test for duplicate GET_DIR_DELEGATION requests Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 05/26] server41tests: pass_warn() when server doesn't support dir delegations Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 06/26] server41tests: test remove triggers dir delegation recall Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 07/26] server41tests: test rename " Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 08/26] server41tests: test mkdir " Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 09/26] server41tests: test link " Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 10/26] server41tests: test no notifications without GFLAG_EXTEND Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 11/26] server41tests: test unrequested notification type triggers recall Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 12/26] server41tests: add a test for removal from dir with dir delegation Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 13/26] server41tests: add a test for directory add notifications Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 14/26] server41tests: add test for RENAME event notifications Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 15/26] server41tests: verify child attributes in ADD notification Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 16/26] server41tests: test CHANGE_DIR_ATTRS notification Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 17/26] server41tests: test mkdir triggers ADD notification Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 18/26] server41tests: test DELEGRETURN stops notifications Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 19/26] server41tests: verify filehandle in ADD notification Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 20/26] server41tests: test cross-directory rename REMOVE notification Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 21/26] server41tests: test cross-directory rename ADD notification on target Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 22/26] server41tests: test link triggers ADD notification Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 23/26] server41tests: test same-client changes don't trigger notifications Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 24/26] server41tests: test cross-directory rename-over nad_old_entry Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 25/26] server41tests: test within-directory " Jeff Layton
2026-06-19 19:22 ` [PATCH pynfs v3 26/26] nfs4.1: move a lot of log/log_cb.info messages to log/log_cb.debug Jeff Layton
2026-06-23 21:33 ` Calum Mackay [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=ebb03dbb-df8c-4270-9bd1-9a2fa64b7e18@oracle.com \
--to=calum.mackay@oracle.com \
--cc=Dai.Ngo@oracle.com \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=smayhew@redhat.com \
--cc=tom@talpey.com \
--cc=trondmy@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