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] first round of v6.6 fixes for nfsd
Date: Fri, 15 Sep 2023 16:05:16 +0000 [thread overview]
Message-ID: <63D87D8F-8513-4B12-BA9B-752BD5C7D4FD@oracle.com> (raw)
The following changes since commit b38a6023da6a12b561f0421c6a5a1f7624a1529c:
Documentation: Add missing documentation for EXPORT_OP flags (2023-08-29 17:45:22 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-6.6-1
for you to fetch changes up to 88956eabfdea7d01d550535af120d4ef265b1d02:
NFSD: fix possible oops when nfsd/pool_stats is closed. (2023-09-12 09:39:35 -0400)
----------------------------------------------------------------
nfsd-6.6 fixes:
- Use correct order when encoding NFSv4 RENAME change_info
- Fix a potential oops during NFSD shutdown
----------------------------------------------------------------
Jeff Layton (1):
nfsd: fix change_info in NFSv4 RENAME replies
NeilBrown (1):
NFSD: fix possible oops when nfsd/pool_stats is closed.
fs/nfsd/nfs4proc.c | 4 ++--
fs/nfsd/nfssvc.c | 5 +++--
2 files changed, 5 insertions(+), 4 deletions(-)
--
Chuck Lever
next reply other threads:[~2023-09-15 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 16:05 Chuck Lever III [this message]
2023-09-16 0:33 ` [GIT PULL] first round of v6.6 fixes for nfsd 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=63D87D8F-8513-4B12-BA9B-752BD5C7D4FD@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