From: Chuck Lever <cel@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-nfs@vger.kernel.org>,
Jeff Layton <jlayton@kernel.org>
Subject: [GIT PULL] Another NFSD fix for v7.2
Date: Tue, 21 Jul 2026 14:15:44 -0400 [thread overview]
Message-ID: <20260721181544.3048006-1-cel@kernel.org> (raw)
The following changes since commit 92ea163c773cb4d0d5eaf103ed80c49d6758b96f:
NFSD: Prevent post-shutdown use-after-free in NFSD_CMD_UNLOCK_FILESYSTEM (2026-07-05 21:09:42 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-7.2-2
for you to fetch changes up to 5c4851e4cdfc3204128f88991be64a6e3929d3d0:
lockd: fix NLMv3 GRANTED_MSG handling (2026-07-17 09:31:50 -0400)
----------------------------------------------------------------
nfsd-7.2 fixes:
Issues reported with v7.2-rc:
- Fix issue with NLMv3 GRANTED_MSG introduced in v7.2
----------------------------------------------------------------
Olga Kornievskaia (1):
lockd: fix NLMv3 GRANTED_MSG handling
fs/lockd/svcproc.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
reply other threads:[~2026-07-21 18:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260721181544.3048006-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox