From: Trond Myklebust <trondmy@kernel.org>
To: linux-nfs@vger.kernel.org
Subject: [PATCH v2 0/8] Assortment of I/O fixes for the NFS client
Date: Sat, 6 Sep 2025 12:42:08 -0400 [thread overview]
Message-ID: <cover.1757176392.git.trond.myklebust@hammerspace.com> (raw)
In-Reply-To: <cover.1757100278.git.trond.myklebust@hammerspace.com>
From: Trond Myklebust <trond.myklebust@hammerspace.com>
The following patch series addresses a series of issues that affect the
NFS client's I/O path. The first patch is needed to fix a corner case
when using mmap() to map the tail end of the file into memory, and then
later extending the file length (see recent xfstests generic/363).
The second set is used to ensure correct ordering of O_DIRECT operations
with truncate + fallocate.
Finally, there are fixes to ensure folio invalidation is correct w.r.t.
the VFS documentation, and a cleanup of the code that decides when a
folio can be marked as up to date.
v2:
- Fix an off by one issue in nfs_write_begin()
- Address eof page pollution on copy offload and clone range (Thanks, Olga!)
- Address O_DIRECT ordering w.r.t. copy offload and clone range
Trond Myklebust (8):
NFS: Protect against 'eof page pollution'
NFSv4.2: Protect copy offload and clone against 'eof page pollution'
NFS: Serialise O_DIRECT i/o and truncate()
NFSv4.2: Serialise O_DIRECT i/o and fallocate()
NFSv4.2: Serialise O_DIRECT i/o and clone range
NFSv4.2: Serialise O_DIRECT i/o and copy range
NFS: nfs_invalidate_folio() must observe the offset and size arguments
NFS: Fix the marking of the folio as up to date
fs/nfs/file.c | 40 +++++++++++++++++++++++++++++++---
fs/nfs/inode.c | 13 +++++++++---
fs/nfs/internal.h | 12 +++++++++++
fs/nfs/io.c | 13 ++----------
fs/nfs/nfs42proc.c | 35 ++++++++++++++++++++++--------
fs/nfs/nfs4file.c | 2 ++
fs/nfs/nfstrace.h | 1 +
fs/nfs/write.c | 53 ++++++----------------------------------------
8 files changed, 96 insertions(+), 73 deletions(-)
--
2.51.0
next prev parent reply other threads:[~2025-09-06 16:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 19:35 [PATCH 0/5] Assortment of I/O fixes for the NFS client Trond Myklebust
2025-09-05 19:35 ` [PATCH 1/5] NFS: Protect against 'eof page pollution' Trond Myklebust
2026-01-24 21:01 ` Lorenzo Stoakes
2026-01-24 22:20 ` Trond Myklebust
2026-01-26 13:03 ` Lorenzo Stoakes
2025-09-05 19:35 ` [PATCH 2/5] NFS: Serialise O_DIRECT i/o and truncate() Trond Myklebust
2025-09-05 19:35 ` [PATCH 3/5] NFSv4.2: Serialise O_DIRECT i/o and fallocate() Trond Myklebust
2025-09-05 19:35 ` [PATCH 4/5] NFS: nfs_invalidate_folio() must observe the offset and size arguments Trond Myklebust
2025-09-05 19:35 ` [PATCH 5/5] NFS: Fix the marking of the folio as up to date Trond Myklebust
2025-09-06 16:42 ` Trond Myklebust [this message]
2025-09-06 16:42 ` [PATCH v2 1/8] NFS: Protect against 'eof page pollution' Trond Myklebust
2025-09-06 16:42 ` [PATCH v2 2/8] NFSv4.2: Protect copy offload and clone " Trond Myklebust
2025-09-06 16:42 ` [PATCH v2 3/8] NFS: Serialise O_DIRECT i/o and truncate() Trond Myklebust
2025-09-06 16:42 ` [PATCH v2 4/8] NFSv4.2: Serialise O_DIRECT i/o and fallocate() Trond Myklebust
2025-09-06 16:42 ` [PATCH v2 5/8] NFSv4.2: Serialise O_DIRECT i/o and clone range Trond Myklebust
2025-09-06 16:42 ` [PATCH v2 6/8] NFSv4.2: Serialise O_DIRECT i/o and copy range Trond Myklebust
2025-09-06 16:42 ` [PATCH v2 7/8] NFS: nfs_invalidate_folio() must observe the offset and size arguments Trond Myklebust
2025-09-06 16:42 ` [PATCH v2 8/8] NFS: Fix the marking of the folio as up to date Trond Myklebust
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=cover.1757176392.git.trond.myklebust@hammerspace.com \
--to=trondmy@kernel.org \
--cc=linux-nfs@vger.kernel.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