From: Hyunchul Lee <hyc.lee@gmail.com>
To: Hongling Zeng <zenghongling@kylinos.cn>
Cc: linkinjeon@kernel.org, ntfs@lists.linux.dev,
linux-kernel@vger.kernel.org, zhongling0719@126.com
Subject: Re: [PATCH 1/2] ntfs: keep the file size on a failed initialized-size extension
Date: Thu, 29 Oct 2026 13:28:10 +0900 [thread overview]
Message-ID: <auLLWhcN3xKsSdB6@hyunchul-PC02> (raw)
In-Reply-To: <20261028080656.1027283-1-zenghongling@kylinos.cn>
On Wed, Oct 28, 2026 at 04:06:55PM +0800, Hongling Zeng wrote:
> ntfs_extend_initialized_size() only extends the initialized size and
> never changes the data size, but on a failure it calls
> truncate_setsize() with the old initialized size, which shrinks the
> VFS size down to it and drops the page cache beyond that point.
>
> None of the callers rolls the shrunk size back. A buffered write
> into a hole has nothing to roll back - the data size never changed -
> so the file keeps the shrunk size even though the data size on disk
> is intact. The mmap and named stream callers return without any
> rollback either.
>
> The sizes did not change, so nothing needs the shrink. Remove it.
>
> Fixes: af0db57d4293 ("ntfs: update inode operations")
> Signed-off-by: Hongling Zeng <zenghongling@kylinos.cn>
Looks good to me.
Reviewed-by: Hyunchul Lee <hyc.lee@gmail.com>
> ---
> fs/ntfs/inode.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/fs/ntfs/inode.c b/fs/ntfs/inode.c
> index 206db4e99ef1..ac13e8776909 100644
> --- a/fs/ntfs/inode.c
> +++ b/fs/ntfs/inode.c
> @@ -2599,8 +2599,6 @@ int ntfs_extend_initialized_size(struct inode *vi, const loff_t offset,
> mutex_lock(&mrec_ni->mrec_lock);
> err = ntfs_attr_set_initialized_size(ni, new_size);
> mutex_unlock(&mrec_ni->mrec_lock);
> - if (err)
> - truncate_setsize(vi, old_init_size);
> out:
> filemap_invalidate_unlock(vi->i_mapping);
> return err;
> --
> 2.25.1
>
--
Thanks,
Hyunchul
next prev parent reply other threads:[~2026-10-29 4:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 8:06 [PATCH 1/2] ntfs: keep the file size on a failed initialized-size extension Hongling Zeng
2026-10-28 8:06 ` [PATCH 2/2] ntfs: fix a self-deadlock on writes to non-resident named streams Hongling Zeng
2026-10-28 8:41 ` liubaolin
2026-10-29 4:28 ` Hyunchul Lee
2026-10-29 8:52 ` Namjae Jeon
2026-10-28 8:41 ` [PATCH 1/2] ntfs: keep the file size on a failed initialized-size extension liubaolin
2026-10-29 4:28 ` Hyunchul Lee [this message]
2026-10-29 8:52 ` Namjae Jeon
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=auLLWhcN3xKsSdB6@hyunchul-PC02 \
--to=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs@lists.linux.dev \
--cc=zenghongling@kylinos.cn \
--cc=zhongling0719@126.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.