From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Nikolay Borisov <nborisov@suse.com>, Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] btrfs: inode: Don't compress if NODATASUM or NODATACOW set
Date: Tue, 15 May 2018 16:30:54 +0800 [thread overview]
Message-ID: <d49bc96a-2a15-b64e-eaa0-47e62ee57fa3@gmx.com> (raw)
In-Reply-To: <9c4e5071-d83b-01db-2c2f-518ee1650713@suse.com>
On 2018年05月15日 16:21, Nikolay Borisov wrote:
>
>
> On 15.05.2018 10:36, Qu Wenruo wrote:
>> As btrfs(5) specified:
>>
>> Note
>> If nodatacow or nodatasum are enabled, compression is disabled.
>>
>> If NODATASUM or NODATACOW set, we should not compress the extent.
>>
>> Normally NODATACOW is detected properly in run_delalloc_range() so
>> compression won't happen for NODATACOW.
>>
>> However for NODATASUM we don't have any check, and it can cause
>> compressed extent without csum pretty easily, just by:
>> ------
>> mkfs.btrfs -f $dev
>> mount $dev $mnt -o nodatasum
>> touch $mnt/foobar
>> mount -o remount,datasum,compress $mnt
>> xfs_io -f -c "pwrite 0 128K" $mnt/foobar
>> ------
>>
>> And in fact, we have bug report about corrupted compressed extent
>> without proper data checksum so even RAID1 can't recover the corruption.
>> (https://bugzilla.kernel.org/show_bug.cgi?id=199707)
>>
>> Running compression without proper checksum could cause more damage when
>> corruption happens, so there is no need to allow compression for
>> NODATACSUM.
>>
>> Reported-by: James Harvey <jamespharvey20@gmail.com>
>> Signed-off-by: Qu Wenruo <wqu@suse.com>
>> ---
>> fs/btrfs/inode.c | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
>> index d241285a0d2a..dbef3f404559 100644
>> --- a/fs/btrfs/inode.c
>> +++ b/fs/btrfs/inode.c
>> @@ -396,6 +396,14 @@ static inline int inode_need_compress(struct inode *inode, u64 start, u64 end)
>> {
>> struct btrfs_fs_info *fs_info = btrfs_sb(inode->i_sb);
>>
>> + /*
>> + * Btrfs doesn't support compression without csum or CoW.
>> + * This should have the highest priority.
>> + */
>> + if (BTRFS_I(inode)->flags & BTRFS_INODE_NODATACOW ||
>> + BTRFS_I(inode)->flags & BTRFS_INODE_NODATASUM)
>> + return 0;
>> +
>
> How is this not buggy, given that if inode_need_compress as called from
> compress_file_range will return zero, meaning we jump to cont: label.
> Then in the case of an inline extent we can execute :
In that case, you won't go into compress_file_range() at all.
As the only caller of compress_file_range() is async_cow_start(), which
get queued in cow_file_range_async().
And cow_file_range_async() traces back to run_delalloc_range().
Here we determine (basically) where some dirty range goes.
The modification in inode_need_compress() mostly affects the decision in
run_delalloc_range(), so we won't go cow_file_range_async(), thus we
won't hit the problem you described.
>
> ret = cow_file_range_inline(inode, start, end,
> total_compressed,
> compress_type, pages);
>
> where compress_type would have been set at the beginning of the
> function unconditionally to fs_info->compress_type.
>
> For non-inline extents I guess we are ok, given that will_compress
> will not be set. However, this code is rather messy and I'm not sure
> it's well defined what's going to happen in this case with inline extents.
>
> OTOH, I think there is something fundamentally wrong in calling
> inode_need_compress in compress_file_range. I.e they work at different
> abstractions. IMO compress_file_range should only be called if we know
> we have to compress the range.
>
> So looking around the code in run_delalloc_range (the only function
> which calls cow_file_range_async) we already have :
>
> } else if (!inode_need_compress(inode, start, end)) {
> ret = cow_file_range(inode, locked_page, start, end, end,
> page_started, nr_written, 1, NULL);
>
> and in the else branch we have the cow_file_range_async. So the code
> is sort of half-way there to actually decoupling compression checking from
> performing the actual compression.
>
>
>> /* force compress */
>> if (btrfs_test_opt(fs_info, FORCE_COMPRESS))
>> return 1;
>
> One more thing, in inode_need_compress shouldn't the inode specific
> checks come first something like :
>
>
> static inline int inode_need_compress(struct inode *inode, u64 start, u64 end)
> {
> struct btrfs_fs_info *fs_info = btrfs_sb(inode->i_sb);
>
> /* defrag ioctl */
> if (BTRFS_I(inode)->defrag_compress)
> return 1;
> /* bad compression ratios */
> if (BTRFS_I(inode)->flags & BTRFS_INODE_NOCOMPRESS)
> return 0;
Not exactly.
Force-compress should less us bypass bad compression ratio, so it should
be at least before ratio check.
Thanks,
Qu
> /* force compress */
> if (btrfs_test_opt(fs_info, FORCE_COMPRESS))
> return 1;
> if (btrfs_test_opt(fs_info, COMPRESS) ||
> BTRFS_I(inode)->flags & BTRFS_INODE_COMPRESS ||
> BTRFS_I(inode)->prop_compress)
> return btrfs_compress_heuristic(inode, start, end);
> return 0;
> }
>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2018-05-15 8:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 7:36 [PATCH 0/2] btrfs: Enhance btrfs handling compression and Qu Wenruo
2018-05-15 7:36 ` [PATCH 1/2] btrfs: inode: Don't compress if NODATASUM or NODATACOW set Qu Wenruo
2018-05-15 8:21 ` Nikolay Borisov
2018-05-15 8:30 ` Qu Wenruo [this message]
2018-05-15 8:35 ` Nikolay Borisov
2018-05-15 8:48 ` Qu Wenruo
2018-05-15 10:36 ` Nikolay Borisov
2018-05-15 10:48 ` Qu Wenruo
2019-06-25 8:24 ` Qu Wenruo
2019-06-27 14:58 ` David Sterba
2019-06-28 1:26 ` Qu Wenruo
2019-06-28 11:34 ` David Sterba
2019-06-28 12:09 ` Qu Wenruo
2019-06-28 16:38 ` David Sterba
2019-06-28 2:47 ` Anand Jain
2019-06-28 5:58 ` Qu Wenruo
2019-06-28 6:56 ` Anand Jain
2019-06-28 7:09 ` Qu Wenruo
2018-05-15 7:36 ` [PATCH 2/2] btrfs: lzo: Avoid decompressing obviously corrupted data Qu Wenruo
2018-05-15 8:05 ` Nikolay Borisov
2018-05-15 8:32 ` Qu Wenruo
2018-05-15 8:34 ` Nikolay Borisov
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=d49bc96a-2a15-b64e-eaa0-47e62ee57fa3@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=wqu@suse.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;
as well as URLs for NNTP newsgroup(s).