From: Anna Schumaker <anna@kernel.org>
To: linux-nfs@vger.kernel.org, trond.myklebust@hammerspace.com
Cc: anna@kernel.org
Subject: [PATCH v2 0/4] NFS: Add directory delegation support for CB_NOTIFY
Date: Tue, 25 Aug 2026 11:02:05 -0400 [thread overview]
Message-ID: <20260825150209.694646-1-anna@kernel.org> (raw)
From: Anna Schumaker <anna.schumaker@hammerspace.com>
These patches add support for the CB_NOTIFY callback operation from NFS
servers. Editing directory order or placement in our caches isn't easy
or practical the way things are structured now. Instead, I use CB_NOTIFY
as an indication that the client needs to refresh its view of the
directory.
Changes in v2:
* Fix signed / unsigned type mixups
* Don't try to share lookup code between NOTIFY4_REMOVE and NOTIFY4_ADD
* Add handling for the NOTIFY4_ADD 'na_have_old_entry' case
Thoughts?
Anna
Anna Schumaker (4):
NFS: Add an outline for the CB_NOTIFY operation
NFS: Add support for CB_NOTIFY4_REMOVE_ENTRY
NFS: Add support for CB_NOTIFY4_ADD_ENTRY
NFS: Add support for CB_NOTIFY4_RENAME_ENTRY
fs/nfs/callback.h | 51 ++++++++++++
fs/nfs/callback_proc.c | 147 ++++++++++++++++++++++++++++++++++
fs/nfs/callback_xdr.c | 175 ++++++++++++++++++++++++++++++++++++++++-
fs/nfs/nfs4_fs.h | 2 +
fs/nfs/nfs4xdr.c | 33 +++++++-
include/linux/nfs4.h | 6 ++
6 files changed, 409 insertions(+), 5 deletions(-)
--
2.55.0
next reply other threads:[~2026-08-25 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 15:02 Anna Schumaker [this message]
2026-08-25 15:02 ` [PATCH v2 1/4] NFS: Add an outline for the CB_NOTIFY operation Anna Schumaker
2026-08-25 15:02 ` [PATCH v2 2/4] NFS: Add support for CB_NOTIFY4_REMOVE_ENTRY Anna Schumaker
2026-08-25 16:11 ` Jeff Layton
2026-08-25 15:02 ` [PATCH v2 3/4] NFS: Add support for CB_NOTIFY4_ADD_ENTRY Anna Schumaker
2026-08-25 15:02 ` [PATCH v2 4/4] NFS: Add support for CB_NOTIFY4_RENAME_ENTRY Anna Schumaker
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=20260825150209.694646-1-anna@kernel.org \
--to=anna@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
/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