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 updates for 6.10
Date: Thu, 23 May 2024 20:30:36 +0000 [thread overview]
Message-ID: <c1293d87d1e91d9986cb03c923f714560a0cc4d0.camel@hammerspace.com> (raw)
Hi Linus,
The following changes since commit a38297e3fb012ddfa7ce0321a7e5a8daeb1872b6:
Linux 6.9 (2024-05-12 14:12:29 -0700)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-6.10-1
for you to fetch changes up to 3c0a2e0b0ae661457c8505fecc7be5501aa7a715:
nfs: fix undefined behavior in nfs_block_bits() (2024-05-21 08:34:15 -0400)
----------------------------------------------------------------
NFS client updates for Linux 6.10
Highlights include:
Stable fixes:
- nfs: fix undefined behavior in nfs_block_bits()
- NFSv4.2: Fix READ_PLUS when server doesn't support OP_READ_PLUS
Bugfixes:
- Fix mixing of the lock/nolock and local_lock mount options
- NFSv4: Fixup smatch warning for ambiguous return
- NFSv3: Fix remount when using the legacy binary mount api
- SUNRPC: Fix the handling of expired RPCSEC_GSS contexts
- SUNRPC: fix the NFSACL RPC retries when soft mounts are enabled
- rpcrdma: fix handling for RDMA_CM_EVENT_DEVICE_REMOVAL
Features and cleanups:
- NFSv3: Use the atomic_open API to fix open(O_CREAT|O_TRUNC)
- pNFS/filelayout: S layout segment range in LAYOUTGET
- pNFS: rework pnfs_generic_pg_check_layout to check IO range
- NFSv2: Turn off enabling of NFS v2 by default
----------------------------------------------------------------
Anna Schumaker (4):
pNFS/filelayout: Remove the whole file layout requirement
pNFS/filelayout: Specify the layout segment range in LAYOUTGET
NFS: Fix READ_PLUS when server doesn't support OP_READ_PLUS
NFS: Don't enable NFS v2 by default
Benjamin Coddington (1):
NFSv4: Fixup smatch warning for ambiguous return
Chen Hanxiao (1):
NFS: make sure lock/nolock overriding local_lock mount option
Dan Aloni (2):
sunrpc: fix NFSACL RPC retry on soft mount
rpcrdma: fix handling for RDMA_CM_EVENT_DEVICE_REMOVAL
Martin Kaiser (1):
nfs: keep server info for remounts
NeilBrown (1):
NFS: add atomic_open for NFSv3 to handle O_TRUNC correctly.
Olga Kornievskaia (4):
SUNRPC: fix handling expired GSS context
pNFS/filelayout: fixup pNfs allocation modes
pNFS/filelayout: check layout segment range
pNFS: rework pnfs_generic_pg_check_layout to check IO range
Sergey Shtylyov (1):
nfs: fix undefined behavior in nfs_block_bits()
fs/nfs/Kconfig | 4 +--
fs/nfs/dir.c | 54 ++++++++++++++++++++++++++++++++--
fs/nfs/filelayout/filelayout.c | 24 +++++----------
fs/nfs/flexfilelayout/flexfilelayout.c | 12 ++------
fs/nfs/fs_context.c | 11 +++++--
fs/nfs/internal.h | 11 +++++--
fs/nfs/nfs3proc.c | 1 +
fs/nfs/nfs4proc.c | 2 +-
fs/nfs/nfs4state.c | 12 ++++----
fs/nfs/pnfs.c | 29 ++++++------------
fs/nfs/pnfs.h | 3 +-
fs/nfs/proc.c | 1 +
fs/nfs/super.c | 10 +++++++
include/linux/nfs_fs.h | 3 ++
net/sunrpc/clnt.c | 14 ++++++++-
net/sunrpc/xprtrdma/verbs.c | 6 +++-
16 files changed, 129 insertions(+), 68 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next reply other threads:[~2024-05-23 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 20:30 Trond Myklebust [this message]
2024-05-23 20:55 ` [GIT PULL] Please pull NFS client updates for 6.10 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=c1293d87d1e91d9986cb03c923f714560a0cc4d0.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).