From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Nikolay Borisov <nborisov@suse.com>,
Haowen Bai <baihaowen@meizu.com>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: Fix a memory leak in btrfs_ioctl_balance()
Date: Thu, 21 Apr 2022 19:41:15 +0800 [thread overview]
Message-ID: <e876305b-5497-22bd-e0d1-bfd8d9289ff0@gmx.com> (raw)
In-Reply-To: <c7d16718-1071-2b57-fc77-968945cfb4f5@suse.com>
On 2022/4/21 19:25, Nikolay Borisov wrote:
>
>
> On 21.04.22 г. 14:21 ч., Nikolay Borisov wrote:
>>
>>
>> On 21.04.22 г. 12:51 ч., Haowen Bai wrote:
>>> Free "bargs" before return.
>>>
>>> Signed-off-by: Haowen Bai <baihaowen@meizu.com>
>>> ---
>>> fs/btrfs/ioctl.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
>>> index f08233c2b0b2..d4c8bea914b7 100644
>>> --- a/fs/btrfs/ioctl.c
>>> +++ b/fs/btrfs/ioctl.c
>>> @@ -4389,13 +4389,13 @@ static long btrfs_ioctl_balance(struct file
>>> *file, void __user *arg)
>>> /* this is (2) */
>>> mutex_unlock(&fs_info->balance_mutex);
>>> ret = -EINPROGRESS;
>>> - goto out;
>>> + goto out_bargs;
>>> }
>>> } else {
>>> /* this is (1) */
>>> mutex_unlock(&fs_info->balance_mutex);
>>> ret = BTRFS_ERROR_DEV_EXCL_RUN_IN_PROGRESS;
>>> - goto out;
>>> + goto out_bargs;
>>> }
>>> locked:
>>
>> I think this is a better fix:
>>
>> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
>> index 7a6974e877f4..906ed1b93654 100644
>> --- a/fs/btrfs/ioctl.c
>> +++ b/fs/btrfs/ioctl.c
>> @@ -4391,15 +4391,13 @@ static long btrfs_ioctl_balance(struct file
>> *file, void __user *arg)
>> goto again;
>> } else {
>> /* this is (2) */
>> - mutex_unlock(&fs_info->balance_mutex);
>> ret = -EINPROGRESS;
>> - goto out;
>> + goto out_bargs;
>> }
>> } else {
>> /* this is (1) */
>> - mutex_unlock(&fs_info->balance_mutex);
>> ret = BTRFS_ERROR_DEV_EXCL_RUN_IN_PROGRESS;
>> - goto out;
>> + goto out_bargs;
>> }
>>
>> locked:
>>
>
>
> Actually to simplify further:
>
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index 7a6974e877f4..bbda55d41a06 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -4353,6 +4353,7 @@ static long btrfs_ioctl_balance(struct file *file,
> void __user *arg)
> bargs = memdup_user(arg, sizeof(*bargs));
> if (IS_ERR(bargs)) {
> ret = PTR_ERR(bargs);
> + bargs = NULL;
> goto out;
> }
>
> @@ -4391,13 +4392,11 @@ static long btrfs_ioctl_balance(struct file
> *file, void __user *arg)
> goto again;
> } else {
> /* this is (2) */
> - mutex_unlock(&fs_info->balance_mutex);
> ret = -EINPROGRESS;
> goto out;
> }
> } else {
> /* this is (1) */
> - mutex_unlock(&fs_info->balance_mutex);
> ret = BTRFS_ERROR_DEV_EXCL_RUN_IN_PROGRESS;
> goto out;
> }
> @@ -4406,7 +4405,7 @@ static long btrfs_ioctl_balance(struct file *file,
> void __user *arg)
> if (bargs->flags & BTRFS_BALANCE_RESUME) {
> if (!fs_info->balance_ctl) {
> ret = -ENOTCONN;
> - goto out_bargs;
> + goto out;
> }
>
> bctl = fs_info->balance_ctl;
> @@ -4420,18 +4419,18 @@ static long btrfs_ioctl_balance(struct file
> *file, void __user *arg)
>
> if (bargs->flags & ~(BTRFS_BALANCE_ARGS_MASK |
> BTRFS_BALANCE_TYPE_MASK)) {
> ret = -EINVAL;
> - goto out_bargs;
> + goto out;
> }
>
> if (fs_info->balance_ctl) {
> ret = -EINPROGRESS;
> - goto out_bargs;
> + goto out;
> }
>
> bctl = kzalloc(sizeof(*bctl), GFP_KERNEL);
> if (!bctl) {
> ret = -ENOMEM;
> - goto out_bargs;
> + goto out;
> }
>
> memcpy(&bctl->data, &bargs->data, sizeof(bctl->data));
> @@ -4457,12 +4456,11 @@ static long btrfs_ioctl_balance(struct file
> *file, void __user *arg)
> }
>
> kfree(bctl);
> -out_bargs:
This looks much better, without the extra label it's easier to read.
But, the @need_unlock variable seems to be uninitialized now, as it's
only set in case (3), but case (2) and (1) now goes through out which
needs to check @need_unlock.
Thanks,
Qu
> +out:
> kfree(bargs);
> mutex_unlock(&fs_info->balance_mutex);
> if (need_unlock)
> btrfs_exclop_finish(fs_info);
> -out:
> mnt_drop_write_file(file);
> return ret;
> }
>
>
>
>
next prev parent reply other threads:[~2022-04-21 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 9:51 [PATCH] btrfs: Fix a memory leak in btrfs_ioctl_balance() Haowen Bai
2022-04-21 10:01 ` Qu Wenruo
2022-04-21 10:47 ` Filipe Manana
2022-04-21 11:21 ` Nikolay Borisov
2022-04-21 11:25 ` Nikolay Borisov
2022-04-21 11:34 ` Nikolay Borisov
2022-04-21 13:30 ` David Sterba
2022-04-21 11:41 ` Qu Wenruo [this message]
2022-04-21 17:35 ` kernel test robot
2022-04-22 20:28 ` 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=e876305b-5497-22bd-e0d1-bfd8d9289ff0@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=baihaowen@meizu.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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