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 set of fixes for nfsd-6.7
Date: Fri, 17 Nov 2023 14:29:34 +0000 [thread overview]
Message-ID: <BE7C5C79-819A-4971-87C5-DB6CCFBFD1FE@oracle.com> (raw)
Hi Linus-
The following changes since commit 3fd2ca5be07f6a43211591a45b43df9e7b6eba00:
svcrdma: Fix tracepoint printk format (2023-10-16 12:44:40 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-6.7-1
for you to fetch changes up to 264e064fa28c3a9ca56b008bf2a66e93c2a62448:
NFSD: Fix checksum mismatches in the duplicate reply cache (2023-11-11 14:22:27 -0500)
----------------------------------------------------------------
nfsd-6.7 fixes:
- Fix several long-standing bugs in the duplicate reply cache
- Fix a memory leak
----------------------------------------------------------------
Chuck Lever (3):
NFSD: Update nfsd_cache_append() to use xdr_stream
NFSD: Fix "start of NFS reply" pointer passed to nfsd_cache_update()
NFSD: Fix checksum mismatches in the duplicate reply cache
Mahmoud Adam (1):
nfsd: fix file memleak on client_opens_release
fs/nfsd/cache.h | 4 ++--
fs/nfsd/nfs4state.c | 2 +-
fs/nfsd/nfscache.c | 85 ++++++++++++++++++++++++++++++++++++++++++++++++++-----------------------------------
fs/nfsd/nfssvc.c | 14 ++++++++++++--
4 files changed, 65 insertions(+), 40 deletions(-)
--
Chuck Lever
next reply other threads:[~2023-11-17 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 14:29 Chuck Lever III [this message]
2023-11-17 14:39 ` [GIT PULL]: first set of fixes for nfsd-6.7 Jeff Layton
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=BE7C5C79-819A-4971-87C5-DB6CCFBFD1FE@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