From: Chuck Lever <cel@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-nfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Jeff Layton <jlayton@kernel.org>
Subject: [GIT PULL] NFSD fixes for v7.1-rc
Date: Fri, 15 May 2026 10:14:26 -0400 [thread overview]
Message-ID: <20260515141426.357776-1-cel@kernel.org> (raw)
The following changes since commit d644a698de12e996778657f65a4608299368e138:
NFSD: Docs: clean up pnfs server timeout docs (2026-04-03 09:29:32 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-7.1-1
for you to fetch changes up to 4f8ef58c10bfe5f86a643c7c8331b37e69e3dae1:
NFSD: Fix infinite loop in layout state revocation (2026-05-10 12:41:08 -0400)
----------------------------------------------------------------
nfsd-7.1 fixes:
Issues reported with v7.1-rc:
- Correctness fix for the new sunrpc cache netlink protocol
Issues that need expedient stable backports:
- Correctness fixes for delegated attributes
- Prevent an infinite loop when revoking layouts
----------------------------------------------------------------
Chuck Lever (1):
NFSD: Fix infinite loop in layout state revocation
Jeff Layton (1):
sunrpc: start cache request seqno at 1 to fix netlink GET_REQS
Olga Kornievskaia (3):
nfsd: fix GET_DIR_DELEGATION when VFS leases are disabled
nfsd: update mtime/ctime on CLONE in presense of delegated attributes
nfsd: update mtime/ctime on COPY in presence of delegated attributes
Scott Mayhew (1):
nfsd: fix file change detection in CB_GETATTR
fs/nfsd/nfs4proc.c | 18 ++++++++++-----
fs/nfsd/nfs4state.c | 64 ++++++++++++++++++++++++++++++++++++-----------------
fs/nfsd/state.h | 1 +
fs/nfsd/xdr4.h | 1 +
net/sunrpc/cache.c | 2 +-
5 files changed, 60 insertions(+), 26 deletions(-)
next reply other threads:[~2026-05-15 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 14:14 Chuck Lever [this message]
2026-05-15 22:14 ` [GIT PULL] NFSD fixes for v7.1-rc pr-tracker-bot
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=20260515141426.357776-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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.