From: Trond Myklebust <trondmy@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Please pull NFS client bugfixes for Linux 6.19
Date: Thu, 15 Jan 2026 14:46:24 -0500 [thread overview]
Message-ID: <57c6f8f6464f7ba0c0455875d4c53a0f9bf01a2c.camel@kernel.org> (raw)
Hi Linus,
The following changes since commit 3609fa95fb0f2c1b099e69e56634edb8fc03f87c:
Merge tag 'devicetree-fixes-for-6.19-2' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux (2026-01-04 16:57:47 -0800)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-6.19-2
for you to fetch changes up to d5811e6297f3fd9020ac31f51fc317dfdb260cb0:
NFS: Fix size read races in truncate, fallocate and copy offload (2026-01-15 14:38:25 -0500)
----------------------------------------------------------------
NFS client bugfixes for Linux 6.19
Bugfixes:
- NFS: Fix another deadlock involving nfs_release_folio()
- NFS/localio: Stop I/O upon hitting a fatal error
- NFS/localio: Deal with page offsets that are > PAGE_SIZE
- NFS: Fix size read races in truncate, fallocate and copy offload
- NFSv4.x: Several bugfixes for the directory delegation client code
- pNFS: Fix a pNFS-related deadlock when returning delegations during open
- pNFS: Fix memory leaks in various error paths
----------------------------------------------------------------
Anna Schumaker (2):
NFS: Fix directory delegation verifier checks
NFS: Don't immediately return directory delegations when disabled
Trond Myklebust (8):
pNFS: Fix a deadlock when returning a delegation during open()
NFS: Fix a deadlock involving nfs_release_folio()
NFSv4: Fix nfs_clear_verifier_delegated() for delegated directories
NFSv4: Don't free slots prematurely if requesting a directory delegation
NFSv4.x: Directory delegations don't require any state recovery
NFS/localio: Stop further I/O upon hitting an error
NFS/localio: Deal with page bases that are > PAGE_SIZE
NFS: Fix size read races in truncate, fallocate and copy offload
Zilin Guan (2):
pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()
pnfs/blocklayout: Fix memory leak in bl_parse_scsi()
fs/nfs/blocklayout/dev.c | 6 ++-
fs/nfs/delegation.c | 7 ++-
fs/nfs/dir.c | 78 ++++++++++++++++++++-----------
fs/nfs/file.c | 3 +-
fs/nfs/flexfilelayout/flexfilelayoutdev.c | 2 +-
fs/nfs/inode.c | 10 ++--
fs/nfs/io.c | 2 +
fs/nfs/localio.c | 32 ++++++-------
fs/nfs/nfs42proc.c | 29 ++++++++----
fs/nfs/nfs4proc.c | 53 ++++++++++++++++-----
fs/nfs/nfs4state.c | 6 ++-
fs/nfs/nfstrace.h | 3 ++
fs/nfs/pnfs.c | 58 ++++++++++++++++-------
fs/nfs/pnfs.h | 17 +++----
fs/nfs/write.c | 33 +++++++++++++
include/linux/nfs_fs.h | 1 +
16 files changed, 239 insertions(+), 101 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trondmy@kernel.org, trond.myklebust@hammerspace.com
next reply other threads:[~2026-01-15 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 19:46 Trond Myklebust [this message]
2026-01-15 20:09 ` 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=57c6f8f6464f7ba0c0455875d4c53a0f9bf01a2c.camel@kernel.org \
--to=trondmy@kernel.org \
--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®