From: Chuck Lever III <chuck.lever@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeff Layton <jlayton@kernel.org>
Subject: [GIT PULL] late nfsd fixes for 6.5-rc
Date: Thu, 24 Aug 2023 19:58:23 +0000 [thread overview]
Message-ID: <DCE0F098-3F69-4C3A-A74B-34F4E6AF0AA5@oracle.com> (raw)
Hi Linus-
Two last-minute one-liners for v6.5-rc. One got lost in the shuffle,
and the other was reported just this morning.
I have not waited for a cycle in linux-next since we are so near to
the close of v6.5. But these seem pretty low-risk.
-----
The following changes since commit 101df45e7ec36f470559c8fdab8e272cb991ef42:
nfsd: Fix reading via splice (2023-07-30 18:07:12 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-6.5-5
for you to fetch changes up to 8073a98e95323abdea5491533bf5cb51e0ba18d9:
NFSD: Fix a thinko introduced by recent trace point changes (2023-08-24 10:56:28 -0400)
----------------------------------------------------------------
nfsd-6.5 fixes:
- Close race window when handling FREE_STATEID operations
- Fix regression in /proc/fs/nfsd/v4_end_grace introduced in v6.5-rc
----------------------------------------------------------------
Benjamin Coddington (1):
nfsd: Fix race to FREE_STATEID and cl_revoked
Chuck Lever (1):
NFSD: Fix a thinko introduced by recent trace point changes
fs/nfsd/nfs4state.c | 2 +-
fs/nfsd/nfsctl.c | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
--
Chuck Lever
next reply other threads:[~2023-08-24 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 19:58 Chuck Lever III [this message]
2023-08-24 23:15 ` 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=DCE0F098-3F69-4C3A-A74B-34F4E6AF0AA5@oracle.com \
--to=chuck.lever@oracle.com \
--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
all inboxes | Powered by JetHome®