From: Chuck Lever <cel@kernel.org>
To: NeilBrown <neil@brown.name>, Jeff Layton <jlayton@kernel.org>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: <linux-nfs@vger.kernel.org>
Subject: [PATCH v1 0/7] NFSD short subjects
Date: Sun, 4 Oct 2026 15:40:22 -0400 [thread overview]
Message-ID: <20261004194029.10714-1-cel@kernel.org> (raw)
This series of patches addresses several minor issues discovered
while reviewing recent on-list bug reports and fixes.
Chuck Lever (7):
nfsd: use direct I/O only for the last operation in a COMPOUND
nfsd: account for page_base when advancing rq_next_page
nfsd: locate the READ sink page from the reply buffer
nfsd: keep spliced pages below rq_next_page when a READ fails
nfsd: remove unreachable cancel of the layout fence work
sunrpc: preserve rq_daddrlen across request deferral
sunrpc: assign RQ_LOCAL from the transport on every receive
fs/nfsd/nfs4layouts.c | 7 -----
fs/nfsd/nfs4xdr.c | 26 +++++++++++------
fs/nfsd/vfs.c | 67 ++++++++++++++++++++++++++++---------------
fs/nfsd/vfs.h | 3 +-
net/sunrpc/svc_xprt.c | 4 +++
net/sunrpc/svcsock.c | 2 --
6 files changed, 66 insertions(+), 43 deletions(-)
--
2.55.0
next reply other threads:[~2026-10-04 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 19:40 Chuck Lever [this message]
2026-10-04 19:40 ` [PATCH v1 1/7] nfsd: use direct I/O only for the last operation in a COMPOUND Chuck Lever
2026-10-04 19:40 ` [PATCH v1 2/7] nfsd: account for page_base when advancing rq_next_page Chuck Lever
2026-10-04 19:40 ` [PATCH v1 3/7] nfsd: locate the READ sink page from the reply buffer Chuck Lever
2026-10-04 19:40 ` [PATCH v1 4/7] nfsd: keep spliced pages below rq_next_page when a READ fails Chuck Lever
2026-10-04 19:40 ` [PATCH v1 5/7] nfsd: remove unreachable cancel of the layout fence work Chuck Lever
2026-10-04 19:40 ` [PATCH v1 6/7] sunrpc: preserve rq_daddrlen across request deferral Chuck Lever
2026-10-04 19:40 ` [PATCH v1 7/7] sunrpc: assign RQ_LOCAL from the transport on every receive 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=20261004194029.10714-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=dai.ngo@oracle.com \
--cc=jlayton@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.