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/2] nfsd: don't use the xdr buf for temporary storage in CB_NOTIFY
Date: Wed, 12 Aug 2026 14:08:13 -0400 [thread overview]
Message-ID: <20260812-dir-deleg-v1-0-411faa713068@kernel.org> (raw)
I posted a patch to fix up a sparse warning with a cast a few days ago
[1], but Chuck objected and wanted to fix this by moving these
(host-endian) allocations out of the xdr stream entirely.
This patchset should do that. Some of them are able to be moved to
temporary stack allocations, but the mask fields need a separate
kmalloc'ed field tracked in struct nfsd4_cb_notify.
Please consider these for v7.4.
[1]: https://lore.kernel.org/linux-nfs/20260803-dir-deleg-v1-1-51be76861821@kernel.org/
Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
Jeff Layton (2):
nfsd: pass caller-provided attrmask storage into nfsd4_setup_notify_entry4()
nfsd: back CB_NOTIFY notify_mask words with per-delegation storage
fs/nfsd/nfs4state.c | 20 +++++++++-----------
fs/nfsd/nfs4xdr.c | 28 ++++++++++++++--------------
fs/nfsd/state.h | 1 +
3 files changed, 24 insertions(+), 25 deletions(-)
---
base-commit: d33023dfd81b31e80fe65c2921993b1a6cd7043c
change-id: 20260812-dir-deleg-98f3bdcb8223
Best regards,
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2026-08-12 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 18:08 Jeff Layton [this message]
2026-08-12 18:08 ` [PATCH 1/2] nfsd: pass caller-provided attrmask storage into nfsd4_setup_notify_entry4() Jeff Layton
2026-08-12 18:08 ` [PATCH 2/2] nfsd: back CB_NOTIFY notify_mask words with per-delegation storage Jeff Layton
2026-08-12 18:58 ` [PATCH 0/2] nfsd: don't use the xdr buf for temporary storage in CB_NOTIFY 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=20260812-dir-deleg-v1-0-411faa713068@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.