mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: liubaolin <liubaolin12138@163.com>
To: Hongling Zeng <zenghongling@kylinos.cn>,
	linkinjeon@kernel.org, hyc.lee@gmail.com
Cc: ntfs@lists.linux.dev, linux-kernel@vger.kernel.org,
	zhongling0719@126.com, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] ntfs: take invalidate_lock in ntfs_setattr_size()
Date: Fri, 28 Aug 2026 14:47:44 +0800	[thread overview]
Message-ID: <ba9fa26c-dd72-48bc-b938-b3cff9a4f323@163.com> (raw)
In-Reply-To: <20260828061607.240845-1-zenghongling@kylinos.cn>



在 2026/8/28 14:16, Hongling Zeng 写道:
> ntfs_setattr_size() updates i_size and resizes the on-disk attribute
> without holding mapping->invalidate_lock.  Page faults take the lock
> shared, so a fault racing the resize can resolve a VCN against the
> transient runlist state of ntfs_non_resident_attr_expand() and fail
> with a spurious SIGBUS, and can interleave with the size-change
> epilogue (truncate_pagecache(), i_size_write(),
> pagecache_isize_extended()).
> 
> Take invalidate_lock exclusively around the whole resize after
> inode_dio_wait(), matching the fallocate path and other filesystems
> such as xfs, which wraps truncate in its mmaplock (= invalidate_lock).
> 
> Fixes: 9c87959601e8 ("ntfs: update file operations")
> Cc: stable@vger.kernel.org
> Signed-off-by: Hongling Zeng <zenghongling@kylinos.cn>
> ---
>   fs/ntfs/file.c | 15 +++++++++++----
>   1 file changed, 11 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/ntfs/file.c b/fs/ntfs/file.c
> index 1969e4f444f7..585ab2145797 100644
> --- a/fs/ntfs/file.c
> +++ b/fs/ntfs/file.c
> @@ -270,18 +270,25 @@ static int ntfs_setattr_size(struct inode *vi, struct iattr *attr)
>   		return err;
>   
>   	inode_dio_wait(vi);
> +
> +	/*
> +	 * Serialize with page faults and pagecache instantiation so that
> +	 * readers cannot observe the size change until the attribute
> +	 * updates below have completed.
> +	 */
> +	filemap_invalidate_lock(vi->i_mapping);
>   	if (attr->ia_size > old_size) {
>   		truncate_pagecache(vi, old_size);
>   		i_size_write(vi, attr->ia_size);
>   		pagecache_isize_extended(vi, old_size, attr->ia_size);
> -	} else
> +	} else {
>   		truncate_setsize(vi, attr->ia_size);
> +	}
>   
>   	err = ntfs_truncate_vfs(vi, attr->ia_size, old_size);
> -	if (err) {
> +	if (err)
>   		i_size_write(vi, old_size);
> -		return err;
> -	}
> +	filemap_invalidate_unlock(vi->i_mapping);
>   
>   	return err;
>   }

Looks good to me.
Reviewed-by: Baolin Liu <liubaolin@kylinos.cn>


  parent reply	other threads:[~2026-08-28  6:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28  6:16 Hongling Zeng
2026-08-28  6:16 ` [PATCH 2/2] ntfs: take invalidate_lock in ntfs_filemap_page_mkwrite() Hongling Zeng
2026-08-28  6:53   ` liubaolin
2026-08-31  5:56   ` Hyunchul Lee
2026-08-31  7:24   ` Namjae Jeon
2026-08-31  8:21     ` Hongling Zeng
2026-08-28  6:47 ` liubaolin [this message]
2026-08-31  5:54 ` [PATCH 1/2] ntfs: take invalidate_lock in ntfs_setattr_size() Hyunchul Lee

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=ba9fa26c-dd72-48bc-b938-b3cff9a4f323@163.com \
    --to=liubaolin12138@163.com \
    --cc=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=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 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®