From: Miao Xie <miaox@cn.fujitsu.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH V3 1/2] Btrfs: cleanup duplicated division functions
Date: Mon, 24 Sep 2012 10:05:02 +0800 [thread overview]
Message-ID: <505FBFCE.3010503@cn.fujitsu.com> (raw)
In-Reply-To: <20120923114924.GA1975@zambezi.lan>
On Sun, 23 Sep 2012 14:49:24 +0300, Ilya Dryomov wrote:
>> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
>> index 9384a2a..d8d53f7 100644
>> --- a/fs/btrfs/ioctl.c
>> +++ b/fs/btrfs/ioctl.c
>> @@ -3335,6 +3335,24 @@ static long btrfs_ioctl_balance(struct file *file, void __user *arg)
>>
>> goto do_balance;
>> }
>> +
>> + if ((bargs->data.flags & BTRFS_BALANCE_ARGS_USAGE) &&
>> + (bargs->data.usage < 0 || bargs->data.usage > 100)) {
>> + ret = -EINVAL;
>> + goto out_bargs;
>> + }
>> +
>> + if ((bargs->meta.flags & BTRFS_BALANCE_ARGS_USAGE) &&
>> + (bargs->meta.usage < 0 || bargs->meta.usage > 100)) {
>> + ret = -EINVAL;
>> + goto out_bargs;
>> + }
>> +
>> + if ((bargs->sys.flags & BTRFS_BALANCE_ARGS_USAGE) &&
>> + (bargs->sys.usage < 0 || bargs->sys.usage > 100)) {
>> + ret = -EINVAL;
>> + goto out_bargs;
>> + }
>> } else {
>> bargs = NULL;
>> }
>
> Why not drop this hunk ...
Generally, we should check the value when it is input. If not, we might
run our program with the wrong value, and it is possible to cause unknown
problems. So I think the above chunk is necessary.
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index 6019fb2..ff86f91 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -2334,8 +2334,13 @@ static int chunk_usage_filter(struct btrfs_fs_info *fs_info, u64 chunk_offset,
> cache = btrfs_lookup_block_group(fs_info, chunk_offset);
> chunk_used = btrfs_block_group_used(&cache->item);
>
> - BUG_ON(bargs->usage < 0 || bargs->usage > 100);
> - user_thresh = div_factor(cache->key.offset, bargs->usage);
> + if (bargs->usage == 0)
> + user_thresh = 0;
> + else if (bargs->usage >= 100)
> + user_thresh = cache->key.offset;
> + else
> + user_thresh = div_factor(cache->key.offset, bargs->usage);
> +
> if (chunk_used < user_thresh)
> ret = 0;
>
> (diff is on top of the patch in question)
>
> This is the most straightforward transformation I can think of. It
> doesn't result in an unnecessary BUG_ON, keeps churn to a minimum and
agree with you.
> doesn't change the "style" of the balance ioctl. (If I were to check
> every filter argument that way, btrfs_balance_ioctl() would be very long
> and complicated.)
I think the check in btrfs_balance_ioctl() is necessary, the reason is above.
Thanks
Miao
next prev parent reply other threads:[~2012-09-24 2:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 10:51 [PATCH 1/2] Btrfs: cleanup duplicated division functions Miao Xie
2012-09-14 13:54 ` David Sterba
2012-09-17 2:21 ` Miao Xie
2012-09-17 12:07 ` Ilya Dryomov
2012-09-17 16:31 ` David Sterba
2012-09-18 3:53 ` Miao Xie
2012-09-20 2:57 ` [PATCH V2 " Miao Xie
2012-09-20 13:28 ` David Sterba
2012-09-21 8:26 ` Miao Xie
2012-09-21 9:07 ` [PATCH V3 " Miao Xie
2012-09-21 15:24 ` David Sterba
2012-09-23 9:54 ` Miao Xie
2012-09-24 16:33 ` David Sterba
2012-09-23 11:49 ` Ilya Dryomov
2012-09-24 2:05 ` Miao Xie [this message]
2012-09-24 16:47 ` David Sterba
2012-09-24 18:42 ` Ilya Dryomov
2012-09-25 10:24 ` Miao Xie
2012-09-27 10:15 ` Miao Xie
2012-09-27 10:19 ` [PATCH V4 " Miao Xie
2012-09-27 16:56 ` Ilya Dryomov
2012-09-28 1:30 ` Miao Xie
2012-09-28 1:49 ` [PATCH V5 " Miao Xie
2012-09-28 10:09 ` David Sterba
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=505FBFCE.3010503@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=idryomov@gmail.com \
--cc=linux-btrfs@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).