From: Trond Myklebust <trondmy@hammerspace.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client bugfixes for Linux 6.5
Date: Mon, 21 Aug 2023 15:24:23 +0000 [thread overview]
Message-ID: <10efd849aa3c182bae0009523ad9c5fbe3be4e8b.camel@hammerspace.com> (raw)
Hi Linus,
The following changes since commit 5b4a82a0724af1dfd1320826e0266117b6a57fbd:
Revert "NFSv4: Retry LOCK on OLD_STATEID during delegation return" (2023-06-29 14:25:35 -0400)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-6.5-2
for you to fetch changes up to 895cedc1791916e8a98864f12b656702fad0bb67:
xprtrdma: Remap Receive buffers after a reconnect (2023-08-19 10:26:29 -0400)
Thanks,
Trond
----------------------------------------------------------------
NFS client fixes for Linux 6.5
Highlights include:
Stable fixes
- NFS: Fix a use after free in nfs_direct_join_group()
Bugfixes
- NFS: Fix a sysfs server name memory leak
- NFS: Fix a lock recovery hang in NFSv4.0
- NFS: Fix page free in the error path for nfs42_proc_getxattr
- NFS: Fix page free in the error path for __nfs4_get_acl_uncached
- SUNRPC/rdma: Fix receive buffer dma-mapping after a server disconnect
----------------------------------------------------------------
Benjamin Coddington (2):
NFSv4: Fix dropped lock for racing OPEN and delegation return
NFS: Fix sysfs server name memory leak
Chuck Lever (1):
xprtrdma: Remap Receive buffers after a reconnect
Fedor Pchelkin (2):
NFSv4.2: fix error handling in nfs42_proc_getxattr
NFSv4: fix out path in __nfs4_get_acl_uncached
Trond Myklebust (1):
NFS: Fix a use after free in nfs_direct_join_group()
fs/nfs/direct.c | 26 ++++++++++++++++----------
fs/nfs/nfs42proc.c | 5 ++---
fs/nfs/nfs4proc.c | 14 ++++++++++----
fs/nfs/sysfs.c | 4 +++-
net/sunrpc/xprtrdma/verbs.c | 9 ++++-----
5 files changed, 35 insertions(+), 23 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next reply other threads:[~2023-08-21 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 15:24 Trond Myklebust [this message]
2023-08-22 18:01 ` 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=10efd849aa3c182bae0009523ad9c5fbe3be4e8b.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--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®