Commit d9013d15b937 for kernel
commit d9013d15b9379b323f1bcdfff7e7d96df537268a
Author: Hungyu Lin <dennylin0707@gmail.com>
Date: Tue Nov 3 08:34:25 2026 +0000
fuse: clear the old EOF tail before writeback-cache writes
Buffered writeback-cache writes go through iomap_file_buffered_write(),
but do not clear cached data between the old EOF and the write position.
If a shared mapping dirtied the tail of the old EOF page, an extending
write can expose those bytes as file contents instead of zeros. A later
writeback can also send them to the server.
Clear the gap under the existing inode lock before the buffered write.
Use the same page-cache cleanup as fuse_perform_write() does for
write-through writes, leaving the write range itself untouched.
Fixes: 4d99ff8f12eb ("fuse: Turn writeback cache on")
Cc: stable@vger.kernel.org
Signed-off-by: Hungyu Lin <dennylin0707@gmail.com>
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
diff --git a/fs/fuse/file.c b/fs/fuse/file.c
index dcf333aaec17..9e64fe040277 100644
--- a/fs/fuse/file.c
+++ b/fs/fuse/file.c
@@ -1580,6 +1580,11 @@ static ssize_t fuse_cache_write_iter(struct kiocb *iocb, struct iov_iter *from)
written = direct_write_fallback(iocb, from, written,
fuse_perform_write(iocb, from));
} else if (writeback) {
+ loff_t old_size = i_size_read(inode);
+
+ if (iocb->ki_pos > old_size)
+ truncate_pagecache_range(inode, old_size, iocb->ki_pos - 1);
+
/*
* Use iomap so that we can do granular uptodate reads
* and granular dirty tracking for large folios.