From: Chao Yu <yuchao0@huawei.com>
To: <linux-fscrypt@vger.kernel.org>, <linux-ext4@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [PATCH 3/6] f2fs: skip truncate when verity in progress in ->write_begin()
Date: Tue, 13 Aug 2019 10:40:39 +0800 [thread overview]
Message-ID: <13be698c-1a3d-9f6a-66d8-b9024b7963f3@huawei.com> (raw)
In-Reply-To: <20190812225848.GA175194@gmail.com>
Hi Eric,
On 2019/8/13 6:58, Eric Biggers wrote:
> Hi Chao,
>
> On Mon, Aug 12, 2019 at 08:25:33PM +0800, Chao Yu wrote:
>> Hi Eric,
>>
>> On 2019/8/12 5:35, Eric Biggers wrote:
>>> From: Eric Biggers <ebiggers@google.com>
>>>
>>> When an error (e.g. ENOSPC) occurs during f2fs_write_begin() when called
>>> from f2fs_write_merkle_tree_block(), skip truncating the file. i_size
>>> is not meaningful in this case, and the truncation is handled by
>>> f2fs_end_enable_verity() instead.
>>>
>>> Fixes: 60d7bf0f790f ("f2fs: add fs-verity support")
>>> Signed-off-by: Eric Biggers <ebiggers@google.com>
>>> ---
>>> fs/f2fs/data.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
>>> index 3f525f8a3a5fa..00b03fb87bd9b 100644
>>> --- a/fs/f2fs/data.c
>>> +++ b/fs/f2fs/data.c
>>> @@ -2476,7 +2476,7 @@ static void f2fs_write_failed(struct address_space *mapping, loff_t to)
>>> struct inode *inode = mapping->host;
>>> loff_t i_size = i_size_read(inode);
>>>
>>> - if (to > i_size) {
>>
>> Maybe adding one single line comment to mention that it's redundant/unnecessary
>> truncation here is better, if I didn't misunderstand this.
>>
>> Thanks,
>>
>>> + if (to > i_size && !f2fs_verity_in_progress(inode)) {
>>> down_write(&F2FS_I(inode)->i_gc_rwsem[WRITE]);
>>> down_write(&F2FS_I(inode)->i_mmap_sem);
>>>
>
> Do you mean add a comment instead of the !f2fs_verity_in_progress() check, or in
> addition to it? ->write_begin(), ->writepages(), and ->write_end() are all
Sorry, I didn't make this very clear, I meant adding the comment in addition on
above change.
> supposed to ignore i_size when verity is in progress, so I don't think this
> particular part should be different, even if technically it's still correct to
> truncate twice. Also, ext4 needs this check in its ->write_begin() for locking
> reasons; we should keep f2fs similar.
Agreed.
>
> How about having both a comment and the check, like:
>
> /* In the fs-verity case, f2fs_end_enable_verity() does the truncate */
> if (to > i_size && !f2fs_verity_in_progress(inode)) {
The comment looks good to me. :)
Thanks,
>
> - Eric
> .
>
next prev parent reply other threads:[~2019-08-13 2:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 21:35 [PATCH 0/6] fs-verity fixups Eric Biggers
2019-08-11 21:35 ` [PATCH 1/6] fs-verity: fix crash on read error in build_merkle_tree_level() Eric Biggers
2019-08-11 21:35 ` [PATCH 2/6] ext4: skip truncate when verity in progress in ->write_begin() Eric Biggers
2019-08-11 21:35 ` [PATCH 3/6] f2fs: " Eric Biggers
2019-08-12 12:25 ` Chao Yu
2019-08-12 22:58 ` Eric Biggers
2019-08-13 2:40 ` Chao Yu [this message]
2019-08-18 20:24 ` [f2fs-dev] " Eric Biggers
2019-08-11 21:35 ` [PATCH 4/6] ext4: remove ext4_bio_encrypted() Eric Biggers
2019-08-11 21:35 ` [PATCH 5/6] ext4: fix comment in ext4_end_enable_verity() Eric Biggers
2019-08-11 21:35 ` [PATCH 6/6] f2fs: use EFSCORRUPTED in f2fs_get_verity_descriptor() Eric Biggers
2019-08-12 12:26 ` Chao Yu
2019-08-18 20:23 ` [PATCH 0/6] fs-verity fixups Eric Biggers
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=13be698c-1a3d-9f6a-66d8-b9024b7963f3@huawei.com \
--to=yuchao0@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).