From: Chris Mason <mason@kernel.org>
To: mason@kernel.org, tytso@mit.edu, cem@kernel.org,
david@fromorbit.com, jack@suse.cz, djwong@kernel.org,
josef@toxicpanda.com, hch@lst.de, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: [PATCH v6 01/10] xfs: don't skip the flush before shifting extents
Date: Mon, 09 Nov 2026 18:51:12 -0500 [thread overview]
Message-ID: <20261109235111.14129-2-mason@kernel.org> (raw)
In-Reply-To: <20261109235111.14129-1-mason@kernel.org>
On an XFS file larger than 4 EiB, collapse range and insert range can
drop dirty data without writing it back, and then fail with
EFSCORRUPTED.
xfs_prepare_shift() flushes the page cache from its offset to EOF, but
passes i_size as the length. Above 4 EiB the end of that range can
overflow and turn negative. filemap_write_and_wait_range() then writes
nothing, but truncate_pagecache_range() takes the end as unsigned and
drops every folio from the start of the range onward.
A delalloc extent under a dropped folio stays in the data fork, and the
shift returns -EFSCORRUPTED for it.
The fix used here is to pass i_size - offset as the length.
Fixes: 7f9f71be84bc ("xfs: extent shifting doesn't fully invalidate page cache")
Fixes: feeb9b269523 ("filemap: skip write and wait if end offset precedes start")
Signed-off-by: Chris Mason <mason@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
---
fs/xfs/xfs_bmap_util.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/xfs/xfs_bmap_util.c b/fs/xfs/xfs_bmap_util.c
index 865aec3ae5ab..537c6b29417c 100644
--- a/fs/xfs/xfs_bmap_util.c
+++ b/fs/xfs/xfs_bmap_util.c
@@ -980,7 +980,7 @@ xfs_prepare_shift(
* Writeback and invalidate cache for the remainder of the file as we're
* about to shift down every extent from offset to EOF.
*/
- error = xfs_flush_unmap_range(ip, offset, XFS_ISIZE(ip));
+ error = xfs_flush_unmap_range(ip, offset, XFS_ISIZE(ip) - offset);
if (error)
return error;
--
2.55.0
next prev parent reply other threads:[~2026-11-09 23:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 23:51 [PATCH v6 00/10] reflink and atomic write bugs Chris Mason
2026-11-09 23:51 ` Chris Mason [this message]
2026-11-09 23:51 ` [PATCH v6 02/10] xfs: flush the shifted range before changing the file Chris Mason
2026-11-09 23:51 ` [PATCH v6 03/10] xfs: don't change the block map under a dirty folio Chris Mason
2026-11-09 23:51 ` [PATCH v6 04/10] iomap: don't punch delalloc under a dirty EOF block Chris Mason
2026-11-10 9:43 ` Carlos Maiolino
2026-11-11 11:21 ` Christian Brauner
2026-11-11 13:24 ` Carlos Maiolino
2026-11-09 23:51 ` [PATCH v6 05/10] fs: validate atomic writes after O_APPEND and limits Chris Mason
2026-11-10 9:41 ` Carlos Maiolino
2026-11-10 15:26 ` Chris Mason
2026-11-10 16:20 ` Carlos Maiolino
2026-11-09 23:51 ` [PATCH v6 06/10] xfs: recheck direct write alignment after write checks Chris Mason
2026-11-09 23:51 ` [PATCH v6 07/10] xfs: test for reflink after the dio " Chris Mason
2026-11-09 23:51 ` [PATCH v6 08/10] xfs: refuse writes to files racing with realtime inode flag changes Chris Mason
2026-11-09 23:51 ` [PATCH v6 09/10] xfs: refuse fallocate racing with realtime " Chris Mason
2026-11-09 23:51 ` [PATCH v6 10/10] xfs: restart faults " Chris Mason
2026-11-10 9:45 ` [PATCH v6 00/10] reflink and atomic write bugs Carlos Maiolino
2026-11-10 15:56 ` Chris Mason
2026-11-10 16:22 ` Carlos Maiolino
2026-11-10 16:32 ` Chris Mason
2026-11-10 17:00 ` Carlos Maiolino
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=20261109235111.14129-2-mason@kernel.org \
--to=mason@kernel.org \
--cc=cem@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
/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