linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/4] btrfs: fix vanished compression property after failed set
Date: Thu, 14 Mar 2019 16:57:20 +0800	[thread overview]
Message-ID: <4b17143a-0f9d-9be3-3cdf-662972f7ef7f@oracle.com> (raw)
In-Reply-To: <e7d5965a-662f-4b94-6806-f6dd698a55c0@suse.com>



On 3/14/19 4:32 PM, Nikolay Borisov wrote:
> 
> 
> On 14.03.19 г. 7:05 ч., Anand Jain wrote:
>> The compression property resets to NULL, instead of the old value if we
>> fail to set the new compression parameter.
>>
>> btrfs prop get /btrfs compression
>>    compression=lzo
>> btrfs prop set /btrfs compression zli
>>    ERROR: failed to set compression for /btrfs: Invalid argument
>> btrfs prop get /btrfs compression
>>
>> This is because the compression property ->validate() is successful for
>> 'zli' as the strncmp() used the len passed from the userland.
>>
>> Fix it by using the expected string length in strncmp().
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> 
> The changelog could be a bit clearer. The failure is due to the fact
> that ->validate succeeds but ->apply fails and the handling code calls
> > 	btrfs_setxattr(trans, inode, handler->xattr_name,
>                NULL, 0, flags);
> 
> However, if you make this patch be the first in the series you obsolete
> the existing patch 1 and fix the issue in this one. I.e 2 birds with 1
> stone.

  Right. I wanted to show the bugs, its reason, and fix separately.

> Also I believe btrfs/048 could use some extension in the part where it
> validates compression properties to test for the bugs discovered/fixed
> in this series.

  Oh. Let me try. Thanks.

-Anand

>> ---
>>   fs/btrfs/props.c | 6 +++---
>>   1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/btrfs/props.c b/fs/btrfs/props.c
>> index 3cc007e3c7f8..72a06c4d3c70 100644
>> --- a/fs/btrfs/props.c
>> +++ b/fs/btrfs/props.c
>> @@ -275,11 +275,11 @@ static int prop_compression_validate(const char *value, size_t len)
>>   	if (!value)
>>   		return 0;
>>   
>> -	if (!strncmp("lzo", value, len))
>> +	if (!strncmp("lzo", value, 3))
>>   		return 0;
>> -	else if (!strncmp("zlib", value, len))
>> +	else if (!strncmp("zlib", value, 4))
>>   		return 0;
>> -	else if (!strncmp("zstd", value, len))
>> +	else if (!strncmp("zstd", value, 4))
>>   		return 0;
>>   
>>   	return -EINVAL;
>>

  reply	other threads:[~2019-03-14  8:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14  5:05 [PATCH 0/4] btrfs: fix property bugs Anand Jain
2019-03-14  5:05 ` [PATCH 1/4] btrfs: fix zstd compression parameter Anand Jain
2019-03-14  5:05 ` [PATCH 2/4] btrfs: fix vanished compression property after failed set Anand Jain
2019-03-14  8:32   ` Nikolay Borisov
2019-03-14  8:57     ` Anand Jain [this message]
2019-03-14  5:05 ` [PATCH 3/4] btrfs: open code btrfs_set_prop in inherit_prop Anand Jain
2019-03-14  8:57   ` Nikolay Borisov
2019-03-14  9:08     ` Anand Jain
2019-03-14  5:05 ` [PATCH 4/4] btrfs: fix property validate fail should not increment generation Anand Jain

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=4b17143a-0f9d-9be3-3cdf-662972f7ef7f@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@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).