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 6.15
Date: Fri, 16 May 2025 20:38:27 +0000 [thread overview]
Message-ID: <983483fc86a4059a33e11968387f2faca29413ab.camel@hammerspace.com> (raw)
Hi Linus,
The following changes since commit b4432656b36e5cc1d50a1f2dc15357543add530e:
Linux 6.15-rc4 (2025-04-27 15:19:23 -0700)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-6.15-2
for you to fetch changes up to dcd21b609d4abc7303f8683bce4f35d78d7d6830:
NFS: Avoid flushing data while holding directory locks in nfs_rename() (2025-05-16 22:31:35 +0200)
----------------------------------------------------------------
NFS client bugfixes for Linux 6.15
Bugfixes:
- NFS: Fix a couple of missed handlers for the ENETDOWN and ENETUNREACH
transport errors.
- NFS: Handle Oopsable failure of nfs_get_lock_context in the unlock
path.
- NFSv4: Fix a race in nfs_local_open_fh().
- NFSv4/pNFS: Fix a couple of layout segment leaks in layoutreturn.
- NFSv4/pNFS Avoid sharing pNFS DS connections between net namespaces
since IP addresses are not guaranteed to refer to the same nodes.
- NFS: Don't flush file data while holding multiple directory locks in
nfs_rename().
----------------------------------------------------------------
Jeff Layton (2):
nfs: don't share pNFS DS connections between net namespaces
nfs: move the nfs4_data_server_cache into struct nfs_net
Li Lingfeng (1):
nfs: handle failure of nfs_get_lock_context in unlock path
Sergey Shtylyov (2):
nfs: direct: drop useless initializer in nfs_direct_write_completion()
nfs: nfs3acl: drop useless assignment in nfs3_get_acl()
Trond Myklebust (7):
NFSv4: Handle fatal ENETDOWN and ENETUNREACH errors
NFSv4/pnfs: Layoutreturn on close must handle fatal networking errors
pNFS/flexfiles: Record the RPC errors in the I/O tracepoints
NFS/localio: Fix a race in nfs_local_open_fh()
NFSv4/pnfs: Reset the layout state after a layoutreturn
NFS/pnfs: Fix the error path in pnfs_layoutreturn_retry_later_locked()
NFS: Avoid flushing data while holding directory locks in nfs_rename()
fs/nfs/client.c | 9 ++++++
fs/nfs/dir.c | 15 ++++++++-
fs/nfs/direct.c | 2 +-
fs/nfs/filelayout/filelayoutdev.c | 6 ++--
fs/nfs/flexfilelayout/flexfilelayout.c | 6 ++--
fs/nfs/flexfilelayout/flexfilelayoutdev.c | 6 ++--
fs/nfs/localio.c | 2 +-
fs/nfs/netns.h | 6 +++-
fs/nfs/nfs3acl.c | 2 +-
fs/nfs/nfs4proc.c | 18 ++++++++++-
fs/nfs/nfs4trace.h | 34 +++++++++++++--------
fs/nfs/pnfs.c | 51 ++++++++++++++++++++-----------
fs/nfs/pnfs.h | 4 ++-
fs/nfs/pnfs_nfs.c | 32 ++++++++++---------
include/linux/nfs_fs_sb.h | 12 ++++++--
15 files changed, 143 insertions(+), 62 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next reply other threads:[~2025-05-16 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 20:38 Trond Myklebust [this message]
2025-05-16 23:41 ` [GIT PULL] Please pull NFS client bugfixes for 6.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=983483fc86a4059a33e11968387f2faca29413ab.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