From: Chao Yu <chao@kernel.org>
To: wangzijie <wangzijie1@honor.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, niuzhiguo84@gmail.com,
bintian.wang@honor.com, feng.han@honor.com
Subject: Re: [f2fs-dev] [PATCH] f2fs: avoid non-section-aligned size pinned file generation
Date: Mon, 16 Jun 2025 20:26:32 +0800 [thread overview]
Message-ID: <22d8f579-ed67-4c4f-9e62-5e32b8bd0a7d@kernel.org> (raw)
In-Reply-To: <20250613103829.1895191-1-wangzijie1@honor.com>
On 6/13/25 18:38, wangzijie wrote:
> To prevent non-section-aligned size pinned file generated from truncation,
> add check condition in setattr. Meanwhile, clean up F2FS_I_SB.
>
> Signed-off-by: wangzijie <wangzijie1@honor.com>
> ---
> fs/f2fs/file.c | 20 +++++++++++++-------
> 1 file changed, 13 insertions(+), 7 deletions(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index 6bd3de64f..31ecf615b 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -1026,9 +1026,11 @@ int f2fs_setattr(struct mnt_idmap *idmap, struct dentry *dentry,
> {
> struct inode *inode = d_inode(dentry);
> struct f2fs_inode_info *fi = F2FS_I(inode);
> + struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
> + block_t sec_blks = CAP_BLKS_PER_SEC(sbi);
> int err;
>
> - if (unlikely(f2fs_cp_error(F2FS_I_SB(inode))))
> + if (unlikely(f2fs_cp_error(sbi)))
> return -EIO;
>
> if (unlikely(IS_IMMUTABLE(inode)))
> @@ -1047,6 +1049,11 @@ int f2fs_setattr(struct mnt_idmap *idmap, struct dentry *dentry,
> !IS_ALIGNED(attr->ia_size,
> F2FS_BLK_TO_BYTES(fi->i_cluster_size)))
> return -EINVAL;
> + if (f2fs_is_pinned_file(inode) &&
> + attr->ia_size < i_size_read(inode) &&
> + !IS_ALIGNED(attr->ia_size,
> + F2FS_BLK_TO_BYTES(sec_blks)))
F2FS_BLK_TO_BYTES(CAP_BLKS_PER_SEC(sbi))?
as this is the only case we use sec_blks in f2fs_setattr().
And can you please do cleanup on sbi in separated patch?
Thanks,
> + return -EINVAL;
> }
>
> err = setattr_prepare(idmap, dentry, attr);
> @@ -1068,12 +1075,11 @@ int f2fs_setattr(struct mnt_idmap *idmap, struct dentry *dentry,
> }
> if (i_uid_needs_update(idmap, attr, inode) ||
> i_gid_needs_update(idmap, attr, inode)) {
> - f2fs_lock_op(F2FS_I_SB(inode));
> + f2fs_lock_op(sbi);
> err = dquot_transfer(idmap, inode, attr);
> if (err) {
> - set_sbi_flag(F2FS_I_SB(inode),
> - SBI_QUOTA_NEED_REPAIR);
> - f2fs_unlock_op(F2FS_I_SB(inode));
> + set_sbi_flag(sbi, SBI_QUOTA_NEED_REPAIR);
> + f2fs_unlock_op(sbi);
> return err;
> }
> /*
> @@ -1083,7 +1089,7 @@ int f2fs_setattr(struct mnt_idmap *idmap, struct dentry *dentry,
> i_uid_update(idmap, attr, inode);
> i_gid_update(idmap, attr, inode);
> f2fs_mark_inode_dirty_sync(inode, true);
> - f2fs_unlock_op(F2FS_I_SB(inode));
> + f2fs_unlock_op(sbi);
> }
>
> if (attr->ia_valid & ATTR_SIZE) {
> @@ -1144,7 +1150,7 @@ int f2fs_setattr(struct mnt_idmap *idmap, struct dentry *dentry,
> f2fs_mark_inode_dirty_sync(inode, true);
>
> /* inode change will produce dirty node pages flushed by checkpoint */
> - f2fs_balance_fs(F2FS_I_SB(inode), true);
> + f2fs_balance_fs(sbi, true);
>
> return err;
> }
prev parent reply other threads:[~2025-06-16 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 10:38 wangzijie
2025-06-16 12:26 ` Chao Yu [this message]
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=22d8f579-ed67-4c4f-9e62-5e32b8bd0a7d@kernel.org \
--to=chao@kernel.org \
--cc=bintian.wang@honor.com \
--cc=feng.han@honor.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=niuzhiguo84@gmail.com \
--cc=wangzijie1@honor.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®