public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Calum Mackay <calum.mackay@oracle.com>
Cc: 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>,
	linux-nfs@vger.kernel.org,  Jeff Layton <jlayton@kernel.org>
Subject: [PATCH pynfs v2 24/25] server41tests: test cross-directory rename-over nad_old_entry
Date: Thu, 16 Apr 2026 11:14:56 -0700	[thread overview]
Message-ID: <20260416-dir-deleg-v2-24-fad510db5941@kernel.org> (raw)
In-Reply-To: <20260416-dir-deleg-v2-0-fad510db5941@kernel.org>

Test that when a cross-directory rename overwrites an existing file in
a delegated directory, the server reports the overwritten entry via
nad_old_entry in the NOTIFY4_ADD_ENTRY notification rather than
generating a separate NOTIFY4_REMOVE_ENTRY notification.

Per RFC 8881 Section 18.26.4, when the removal is done atomically with
the rename, a separate NOTIFY4_REMOVE_ENTRY notification will not be
generated. Instead, the deletion of the file will be reported as part
of the NOTIFY4_ADD_ENTRY notification via nad_old_entry.

Also fix _getDirDeleg to initialize cb.changes as a list and use
extend() to accumulate notifications, so tests that receive multiple
CB_NOTIFY callbacks can see all notifications.
---
 nfs4.1/server41tests/st_dir_deleg.py | 100 ++++++++++++++++++++++++++++++++++-
 1 file changed, 99 insertions(+), 1 deletion(-)

diff --git a/nfs4.1/server41tests/st_dir_deleg.py b/nfs4.1/server41tests/st_dir_deleg.py
index 63072bd8b81a..a2465efbcdbe 100644
--- a/nfs4.1/server41tests/st_dir_deleg.py
+++ b/nfs4.1/server41tests/st_dir_deleg.py
@@ -44,7 +44,7 @@ def _getDirDeleg(t, env, notify_mask, cb):
     def notify_pre_hook(arg, env):
         cb.stateid = arg.cna_stateid
         cb.fh = arg.cna_fh
-        cb.changes = arg.cna_changes
+        cb.changes.extend(arg.cna_changes)
         cb.got_notify = True
         env.notify = cb.set # This is called after compound sent to queue
     def notify_post_hook(arg, env, res):
@@ -52,6 +52,7 @@ def _getDirDeleg(t, env, notify_mask, cb):
 
     cb.got_recall = False
     cb.got_notify = False
+    cb.changes = []
 
     c = env.c1
     sess1 = c.new_client_session(b"%s_1" % env.testname(t))
@@ -901,3 +902,100 @@ def testDirDelegSameClientNoNotify(t, env):
         fail("Got CB_NOTIFY for delegation holder's own change")
     if cb.got_recall:
         fail("Got CB_RECALL for delegation holder's own change")
+
+def testDirDelegCrossRenameOver(t, env):
+    """Verify cross-directory rename-over reports overwritten entry in nad_old_entry
+
+    Per RFC 8881 Section 18.26.4, when a cross-directory rename
+    overwrites an existing file in the target directory, a
+    NOTIFY4_ADD_ENTRY is generated.  When the removal is done
+    atomically with the rename, a separate NOTIFY4_REMOVE_ENTRY
+    notification will not be generated.  Instead, the deletion of the
+    file will be reported as part of the NOTIFY4_ADD_ENTRY notification
+    via nad_old_entry.
+
+    FLAGS: dirdeleg all
+    CODE: DIRDELEG21
+    """
+    c = env.c1
+    cb = threading.Event()
+
+    # Get a dir delegation on the target directory
+    sess1, fh, deleg = _getDirDeleg(t, env,
+                                     [NOTIFY4_ADD_ENTRY,
+                                      NOTIFY4_REMOVE_ENTRY,
+                                      NOTIFY4_GFLAG_EXTEND], cb)
+
+    topdir = c.homedir + [t.code.encode('utf8')]
+
+    # Create a file in the delegated directory (will be renamed over)
+    victim_name = b"%s_victim" % env.testname(t)
+    claim = open_claim4(CLAIM_NULL, victim_name)
+    owner = open_owner4(0, b"owner")
+    how = openflag4(OPEN4_CREATE, createhow4(GUARDED4, {FATTR4_SIZE:0}))
+    open_op = [ op.putfh(fh), op.open(0,
+                                      OPEN4_SHARE_ACCESS_WRITE | OPEN4_SHARE_ACCESS_WANT_NO_DELEG,
+                                      OPEN4_SHARE_DENY_NONE, owner, how, claim), op.getfh() ]
+    res = sess1.compound(open_op)
+    check(res)
+    open_stateid = res.resarray[-2].stateid
+    file_fh = res.resarray[-1].object
+    close_file(sess1, file_fh, stateid=open_stateid)
+
+    # Create a source directory and a file in it
+    srcdir = c.homedir + [b"%s_src" % t.code.encode('utf8')]
+    res = create_obj(sess1, srcdir)
+    check(res)
+    src_fh = res.resarray[-1].object
+
+    src_name = env.testname(t)
+    claim2 = open_claim4(CLAIM_NULL, src_name)
+    owner2 = open_owner4(0, b"owner2")
+    how2 = openflag4(OPEN4_CREATE, createhow4(GUARDED4, {FATTR4_SIZE:0}))
+    open_op = [ op.putfh(src_fh), op.open(0,
+                                      OPEN4_SHARE_ACCESS_WRITE | OPEN4_SHARE_ACCESS_WANT_NO_DELEG,
+                                      OPEN4_SHARE_DENY_NONE, owner2, how2, claim2), op.getfh() ]
+    res = sess1.compound(open_op)
+    check(res)
+    open_stateid2 = res.resarray[-2].stateid
+    file_fh2 = res.resarray[-1].object
+    close_file(sess1, file_fh2, stateid=open_stateid2)
+
+    # Clear notification state from creates above
+    cb.clear()
+    cb.got_notify = False
+
+    # Rename the source file over the victim in the delegated dir from sess2
+    sess2 = c.new_client_session(b"%s_2" % env.testname(t))
+    oldpath = srcdir + [src_name]
+    newpath = topdir + [victim_name]
+    res = rename_obj(sess2, oldpath, newpath)
+    check(res)
+
+    completed = cb.wait(2)
+    if completed:
+        cb.clear()
+        cb.wait(1)
+
+    delegreturn_op = [ op.putfh(fh), op.delegreturn(deleg) ]
+    res = sess1.compound(delegreturn_op)
+    check(res)
+
+    if (not completed or not cb.got_notify):
+        fail("Didn't receive a CB_NOTIFY from the server!")
+
+    # Look for ADD notification with nad_old_entry for the overwritten file
+    got_add = False
+    for change in cb.changes:
+        evt_type, evt = decode_notify_event(change)
+        if evt_type == NOTIFY4_ADD_ENTRY:
+            got_add = True
+            if evt.nad_new_entry.ne_file != victim_name:
+                fail("Wrong entry name in ADD notification")
+            if len(evt.nad_old_entry) != 1:
+                fail("Expected nad_old_entry to contain the overwritten entry")
+            if evt.nad_old_entry[0].nrm_old_entry.ne_file != victim_name:
+                fail("Wrong overwritten entry name in nad_old_entry")
+
+    if not got_add:
+        fail("Missing ADD notification for cross-dir rename-over")

-- 
2.53.0


  parent reply	other threads:[~2026-04-16 18:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16 18:14 [PATCH pynfs v2 00/25] nfs4.1: add some directory delegation testcases Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 01/25] nfs4.1: add proposed NOTIFY4_GFLAG_EXTEND flag Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 02/25] nfs4.1: add a getfh() to the end of create_obj() compound Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 03/25] server41tests: add a basic GET_DIR_DELEGATION test Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 04/25] server41tests: add a test for duplicate GET_DIR_DELEGATION requests Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 05/25] server41tests: pass_warn() when server doesn't support dir delegations Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 06/25] server41tests: test remove triggers dir delegation recall Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 07/25] server41tests: test rename " Jeff Layton
2026-04-17  0:40   ` Scott Mayhew
2026-04-17 15:42     ` Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 08/25] server41tests: test mkdir " Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 09/25] server41tests: test link " Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 10/25] server41tests: test no notifications without GFLAG_EXTEND Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 11/25] server41tests: test unrequested notification type triggers recall Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 12/25] server41tests: add a test for removal from dir with dir delegation Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 13/25] server41tests: add a test for directory add notifications Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 14/25] server41tests: add test for RENAME event notifications Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 15/25] server41tests: verify child attributes in ADD notification Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 16/25] server41tests: test CHANGE_DIR_ATTRS notification Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 17/25] server41tests: test mkdir triggers ADD notification Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 18/25] server41tests: test DELEGRETURN stops notifications Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 19/25] server41tests: verify filehandle in ADD notification Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 20/25] server41tests: test cross-directory rename REMOVE notification Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 21/25] server41tests: test cross-directory rename ADD notification on target Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 22/25] server41tests: test link triggers ADD notification Jeff Layton
2026-04-16 18:14 ` [PATCH pynfs v2 23/25] server41tests: test same-client changes don't trigger notifications Jeff Layton
2026-04-16 18:14 ` Jeff Layton [this message]
2026-04-16 18:14 ` [PATCH pynfs v2 25/25] server41tests: test within-directory rename-over nad_old_entry 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=20260416-dir-deleg-v2-24-fad510db5941@kernel.org \
    --to=jlayton@kernel.org \
    --cc=Dai.Ngo@oracle.com \
    --cc=anna@kernel.org \
    --cc=calum.mackay@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=okorniev@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