From: Hyunchul Lee <hyc.lee@gmail.com>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>
Cc: Namjae Jeon <linkinjeon@kernel.org>,
ntfs@lists.linux.dev, linux-kernel@vger.kernel.org,
zhanxusheng@xiaomi.com, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] ntfs: don't write a compression block after a short copy
Date: Fri, 6 Nov 2026 10:56:02 +0900 [thread overview]
Message-ID: <au0zsi-oLfcprQxI@hyunchul-PC02> (raw)
In-Reply-To: <f385711f8772132f64462e1d6c13efadadc51bc2.1793874221.git.zhanxusheng@xiaomi.com>
Hi Zhan,
On Thu, Nov 05, 2026 at 09:01:58PM +0800, Zhan Xusheng wrote:
> From: Zhan Xusheng <zhanxusheng@xiaomi.com>
>
> ntfs_compress_write() does not read in the folios of a compression
> block that the write covers completely. If the copy from user space
> then comes up short, the rest of those folios still holds whatever
> the memory held before; ntfs_write_cb() compresses that to disk and
> the folios are marked uptodate.
>
> The copy can come up short after fault_in_iov_iter_readable() has
> succeeded if the source buffer is unmapped in between. On a volume
> with 4K clusters, writing 64K at offset 0 of a compressed file while
> another thread unmaps and remaps the last page of the buffer leaves
> 61440 new bytes followed by 4096 bytes of another process's freed
> memory in the file. The write returns -EFAULT.
>
> Treat a short copy into a full block like a copy that made no
> progress.
>
> Fixes: 5b676a77f3e4 ("ntfs: skip reads for full compression unit overwrites")
> Cc: stable@vger.kernel.org
> Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
This patch looks good to me. But the second patch in this series
appears to be missing.
Reviewed-by: Hyunchul Lee <hyc.lee@gmail.com>
> ---
> Tested in QEMU on ntfs-next with KASAN, 4K clusters, page cache
> dropped and freed memory filled with 'Z' before each write:
>
> before: 16 of 41 writes failed, 3 of them changed the file, each
> time bytes 61440-65535 read back as 0x5a
> after: 286 of 731 writes failed, none changed the file
>
> The same loop on rootfs gives short writes and no corruption. I can
> send the reproducer if it helps.
>
> fs/ntfs/compress.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/fs/ntfs/compress.c b/fs/ntfs/compress.c
> index 82c7c7d29073..287bd47282d9 100644
> --- a/fs/ntfs/compress.c
> +++ b/fs/ntfs/compress.c
> @@ -1567,6 +1567,16 @@ int ntfs_compress_write(struct ntfs_inode *ni, loff_t pos, size_t count,
> }
> }
>
> + /*
> + * The folios of a full compression block are not read in, so
> + * after a short copy the rest of the block holds whatever the
> + * folios contained. Don't write that out.
> + */
> + if (full_cb && copied < cb_size) {
> + iov_iter_revert(from, copied);
> + copied = 0;
> + }
> +
> if (!copied) {
> err = -EFAULT;
> goto release_pages;
>
> base-commit: 564c7753647731d19170914c1c637d3b33d88d3b
> --
> 2.43.0
>
--
Thanks,
Hyunchul
next prev parent reply other threads:[~2026-11-06 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 13:01 Zhan Xusheng
2026-11-06 1:56 ` Hyunchul Lee [this message]
2026-11-06 4:57 ` Zhan Xusheng
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=au0zsi-oLfcprQxI@hyunchul-PC02 \
--to=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=zhanxusheng1024@gmail.com \
--cc=zhanxusheng@xiaomi.com \
/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®