From: Jeff Layton <jlayton@kernel.org>
To: 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>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeff Layton <jlayton@kernel.org>
Subject: [PATCH 0/4] nfsd: follow-on fixes for directory delegations
Date: Sat, 23 May 2026 12:17:33 -0400 [thread overview]
Message-ID: <20260523-dir-deleg-fixes-v1-0-142c884f85ce@kernel.org> (raw)
Just a few small fixes for problems that Sashiko noticed flagged during
review. None are super-critical but it'd be good to have them fixed
before the feature ships.
Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
Jeff Layton (4):
nfsd: check for FILEID_INVALID in setup_notify_fhandle
nfsd: use empty string for directory name in NOTIFY4_CHANGE_DIR_ATTRS
nfsd: check delegation status in nfsd4_cb_notify_done
nfsd: fix ino_t format specifier in nfsd_handle_dir_event tracepoint
fs/nfsd/nfs4state.c | 3 +++
fs/nfsd/nfs4xdr.c | 9 +++------
fs/nfsd/trace.h | 4 ++--
3 files changed, 8 insertions(+), 8 deletions(-)
---
base-commit: 479723a81683c7a5bdaff48ec6968fad3ac1ae24
change-id: 20260523-dir-deleg-fixes-4205d8f25be6
Best regards,
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2026-05-23 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 16:17 Jeff Layton [this message]
2026-05-23 16:17 ` [PATCH 1/4] nfsd: check for FILEID_INVALID in setup_notify_fhandle Jeff Layton
2026-05-23 16:17 ` [PATCH 2/4] nfsd: use empty string for directory name in NOTIFY4_CHANGE_DIR_ATTRS Jeff Layton
2026-05-23 16:17 ` [PATCH 3/4] nfsd: check delegation status in nfsd4_cb_notify_done Jeff Layton
2026-05-23 16:17 ` [PATCH 4/4] nfsd: fix ino_t format specifier in nfsd_handle_dir_event tracepoint Jeff Layton
2026-05-24 12:09 ` Jeff Layton
2026-05-24 17:44 ` Chuck Lever
2026-05-23 17:00 ` [PATCH 0/4] nfsd: follow-on fixes for directory delegations Chuck Lever
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=20260523-dir-deleg-fixes-v1-0-142c884f85ce@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.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
all inboxes | Powered by JetHome®