From: Anna Schumaker <anna@kernel.org>
To: linux-nfs@vger.kernel.org, torvalds@linux-foundation.org
Cc: anna@kernel.org
Subject: [GIT PULL] Please Pull NFS Client Bugfixes for Linux 7.2-rc3
Date: Fri, 10 Jul 2026 16:51:17 -0400 [thread overview]
Message-ID: <20260710205117.622337-1-anna@kernel.org> (raw)
Hi Linus,
The following changes since commit 8cdeaa50eae8dad34885515f62559ee83e7e8dda:
Linux 7.2-rc2 (2026-07-05 14:44:06 -1000)
are available in the Git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-7.2-2
for you to fetch changes up to 27934d02cbeb8a957dd11c985a579e58d30c5270:
NFS: Charge unstable writes by request size, not folio size (2026-07-08 14:43:40 -0400)
----------------------------------------------------------------
NFS Client Bugfixes for Linux 7.2-rc3
Bugfixes:
* SUNRPC: Release lower rpc_clnt if killed waiting for XPRT_LOCKED
* SUNRPC: Pin upper rpc_clnt across the TLS connect_worker
* NFS: Include MAY_WRITE in open permission mask for O_TRUNC
* NFS: Charge unstable writes by request size, not folio size
Thanks,
Anna
----------------------------------------------------------------
Benjamin Coddington (2):
NFSv4: include MAY_WRITE in open permission mask for O_TRUNC
NFS: Charge unstable writes by request size, not folio size
Chuck Lever (2):
SUNRPC: release lower rpc_clnt if killed waiting for XPRT_LOCKED
SUNRPC: pin upper rpc_clnt across the TLS connect_worker
fs/nfs/dir.c | 2 ++
fs/nfs/internal.h | 12 +++++++-----
fs/nfs/pnfs_nfs.c | 2 +-
fs/nfs/write.c | 14 ++++++++------
include/linux/sunrpc/clnt.h | 1 +
net/sunrpc/clnt.c | 19 +++++++++++++++++--
net/sunrpc/xprtsock.c | 16 ++++++++++++++--
7 files changed, 50 insertions(+), 16 deletions(-)
next reply other threads:[~2026-07-10 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 20:51 Anna Schumaker [this message]
2026-07-11 2:00 ` [GIT PULL] Please Pull NFS Client Bugfixes for Linux 7.2-rc3 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=20260710205117.622337-1-anna@kernel.org \
--to=anna@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