From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>, 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/3] nfsd: follow-on fixes for CB_NOTIFY support
Date: Wed, 17 Jun 2026 14:12:28 -0400 [thread overview]
Message-ID: <20260617-dir-deleg-fixes-v1-0-32b85b366c29@kernel.org> (raw)
These are just some problems that Sashiko pointed out in review that
seem to be valid concerns. The Fixes: tags have commit IDs from my tree
that you probably don't have, but they should indicate which patches
these need to be folded into.
Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
Jeff Layton (3):
nfsd: fix CB_NOTIFY workqueue loop when queue overflows
nfsd: fix NULL deref / UAF of sc_export in setup_notify_fhandle
nfsd: recall deleg if a requested dir attr change can't be encoded
fs/nfsd/nfs4state.c | 63 ++++++++++++++++++++++++++++++++++-------------------
fs/nfsd/nfs4xdr.c | 29 +++++++++++++++++++-----
2 files changed, 64 insertions(+), 28 deletions(-)
---
base-commit: fd0d6dde2a57d47d976c936586f0be24669471ec
change-id: 20260617-dir-deleg-fixes-ecac84095b84
Best regards,
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2026-06-17 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 18:12 Jeff Layton [this message]
2026-06-17 18:12 ` [PATCH 1/3] nfsd: fix CB_NOTIFY workqueue loop when queue overflows Jeff Layton
2026-06-17 18:12 ` [PATCH 2/3] nfsd: fix NULL deref / UAF of sc_export in setup_notify_fhandle Jeff Layton
2026-06-17 18:12 ` [PATCH 3/3] nfsd: recall deleg if a requested dir attr change can't be encoded 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=20260617-dir-deleg-fixes-v1-0-32b85b366c29@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=cel@kernel.org \
--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®