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.10
Date: Thu, 13 Jun 2024 15:31:08 +0000 [thread overview]
Message-ID: <789b8f5da4f8a0406fd977f2e067237c51947b45.camel@hammerspace.com> (raw)
Hi Linus,
The following changes since commit 3c0a2e0b0ae661457c8505fecc7be5501aa7a715:
nfs: fix undefined behavior in nfs_block_bits() (2024-05-21 08:34:15 -0400)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-6.10-2
for you to fetch changes up to 99bc9f2eb3f79a2b4296d9bf43153e1d10ca50d3:
NFS: add barriers when testing for NFS_FSDATA_BLOCKED (2024-05-30 16:17:12 -0400)
----------------------------------------------------------------
NFS client bugfixes for Linux 6.10
Bugfixes:
- NFSv4.2: Fix a memory leak in nfs4_set_security_label
- NFSv2/v3: abort nfs_atomic_open_v23 if the name is too long.
- NFS: Add appropriate memory barriers to the sillyrename code
- Propagate readlink errors in nfs_symlink_filler
- NFS: don't invalidate dentries on transient errors
- NFS: fix unnecessary synchronous writes in random write workloads
- NFSv4.1: enforce rootpath check when deciding whether or not to trunk
Other:
- Change email address for Trond Myklebust due to email server concerns
----------------------------------------------------------------
Chen Hanxiao (1):
SUNRPC: return proper error from gss_wrap_req_priv
Dmitry Mastykin (1):
NFSv4: Fix memory leak in nfs4_set_security_label
Jan Kara (1):
nfs: Avoid flushing many pages with NFS_FILE_SYNC
NeilBrown (2):
NFS: abort nfs_atomic_open_v23 if name is too long.
NFS: add barriers when testing for NFS_FSDATA_BLOCKED
Olga Kornievskaia (1):
NFSv4.1 enforce rootpath check in fs_location query
Sagi Grimberg (1):
nfs: propagate readlink errors in nfs_symlink_filler
Scott Mayhew (1):
nfs: don't invalidate dentries on transient errors
Trond Myklebust (1):
MAINTAINERS: Change email address for Trond Myklebust
MAINTAINERS | 2 +-
fs/nfs/dir.c | 77 ++++++++++++++++++++++++++----------------
fs/nfs/nfs4proc.c | 24 ++++++++++++-
fs/nfs/pagelist.c | 5 +++
fs/nfs/symlink.c | 2 +-
net/sunrpc/auth_gss/auth_gss.c | 4 ++-
6 files changed, 81 insertions(+), 33 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next reply other threads:[~2024-06-13 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 15:31 Trond Myklebust [this message]
2024-06-13 19:30 ` 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=789b8f5da4f8a0406fd977f2e067237c51947b45.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®