From: Chao Yu <chao@kernel.org>
To: wangzijie <wangzijie1@honor.com>, linux-f2fs-devel@lists.sourceforge.net
Cc: chao@kernel.org, feng.han@honor.com, jaegeuk@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v4 2/2] f2fs: don't allow unaligned truncation to smaller/equal size on pinned file
Date: Mon, 30 Jun 2025 11:41:39 +0800 [thread overview]
Message-ID: <3c0d3d19-58b2-4702-b42b-1df7985def74@kernel.org> (raw)
In-Reply-To: <20250630025023.3876706-1-wangzijie1@honor.com>
On 6/30/25 10:50, wangzijie wrote:
>> On 6/24/25 11:59, wangzijie wrote:
>>> To prevent scattered pin block generation, don't allow non-section aligned truncation
>>> to smaller or equal size on pinned file. But for truncation to larger size, after
>>> commit 3fdd89b452c2("f2fs: prevent writing without fallocate() for pinned files"),
>>> we only support overwrite IO to pinned file, so we don't need to consider
>>> attr->ia_size > i_size case.
>>
>> Zijie, can you take a look generic/494? suspect that it is caused by this change.
>>
>> generic/494 3s ... - output mismatch (see /share/git/fstests/results//generic/494.out.bad)
>> --- tests/generic/494.out 2025-01-12 21:57:40.279440664 +0800
>> +++ /share/git/fstests/results//generic/494.out.bad 2025-06-30 10:01:37.000000000 +0800
>> @@ -2,7 +2,7 @@
>> Format and mount
>> Initialize file
>> Try to truncate
>> -ftruncate: Text file busy
>> +ftruncate: Invalid argument
>> Try to punch hole
>> fallocate: Text file busy
>> ...
>> (Run 'diff -u /share/git/fstests/tests/generic/494.out /share/git/fstests/results//generic/494.out.bad' to see the entire diff)
>> Ran: generic/494
>> Failures: generic/494
>> Failed 1 of 1 tests
>>
>> Thanks,
>
> Hi, Chao
> generic/494 swapon file and try to ftruncate.
>
> Before this change
> swap_acticate:
> set_inode_flag(inode, FI_PIN_FILE)
>
> ftruncate:
> setattr_prepare
> -inode_newsize_ok
> --return -ETXTBSY for SWAPFILE
>
> After this change:
> swap_acticate:
> set_inode_flag(inode, FI_PIN_FILE)
>
> ftruncate:
> prevent unaligned truncation before setattr_prepare()
> return -EINVAL
>
> Sorry for this. Maybe I should apply this check after setattr_prepare()? Or do
Check after setattr_prepare() looks fine to me, in addition, can you please add
more comments for the reason why we relocate code there?
Thanks,
> you have some suggestions?
>
>
>>>
>>> Signed-off-by: wangzijie <wangzijie1@honor.com>
>>> ---
>>> v4:
>>> - convert sbi first and apply change
>>> ---
>>> fs/f2fs/file.c | 11 +++++++++++
>>> 1 file changed, 11 insertions(+)
>>>
>>> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
>>> index 209f43653..4809f0fd6 100644
>>> --- a/fs/f2fs/file.c
>>> +++ b/fs/f2fs/file.c
>>> @@ -1048,6 +1048,17 @@ 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;
>>> + /*
>>> + * To prevent scattered pin block generation, we don't allow
>>> + * smaller/equal size unaligned truncation for pinned file.
>>> + * We only support overwrite IO to pinned file, so don't
>>> + * care about larger size truncation.
>>> + */
>>> + if (f2fs_is_pinned_file(inode) &&
>>> + attr->ia_size <= i_size_read(inode) &&
>>> + !IS_ALIGNED(attr->ia_size,
>>> + F2FS_BLK_TO_BYTES(CAP_BLKS_PER_SEC(sbi))))
>>> + return -EINVAL;
>>> }
>>>
>>> err = setattr_prepare(idmap, dentry, attr);
>
next prev parent reply other threads:[~2025-06-30 3:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 3:59 [f2fs-dev] [PATCH v4 1/2] f2fs: convert F2FS_I_SB to sbi in f2fs_setattr() wangzijie
2025-06-24 3:59 ` [f2fs-dev] [PATCH v4 2/2] f2fs: don't allow unaligned truncation to smaller/equal size on pinned file wangzijie
2025-06-24 14:19 ` Chao Yu
2025-06-30 2:04 ` Chao Yu
2025-06-30 2:50 ` wangzijie
2025-06-30 3:41 ` Chao Yu [this message]
2025-06-24 14:18 ` [f2fs-dev] [PATCH v4 1/2] f2fs: convert F2FS_I_SB to sbi in f2fs_setattr() Chao Yu
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=3c0d3d19-58b2-4702-b42b-1df7985def74@kernel.org \
--to=chao@kernel.org \
--cc=feng.han@honor.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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®