Linux Btrfs filesystem development
 help / color / mirror / Atom feed
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] btrfs: relocation: Only remove reloc rb_trees if reloc control has been initialized
Date: Mon, 2 Jul 2018 15:53:26 +0800	[thread overview]
Message-ID: <6e41f3cb-9b20-246b-dfc8-ddd5f3ad7441@gmx.com> (raw)
In-Reply-To: <341231a6-8464-d8ee-4e79-fe9066747384@suse.com>



On 2018年07月02日 15:31, Nikolay Borisov wrote:
> 
> 
> On  2.07.2018 09:25, Qu Wenruo wrote:
>> Reported in https://bugzilla.kernel.org/show_bug.cgi?id=199833, where an
>> invalid tree reloc tree can cause kernel NULL pointer dereference when
>> btrfs does some cleanup for reloc roots.
>>
>> It turns out that fs_info->reloc_ctl can be NULL in
>> btrfs_recover_relocation() as we allocate relocation control after all
>> reloc roots are verified.
>> So when we hit out: tag, we haven't call set_reloc_control() thus
>> fs_info->reloc_ctl is still NULL.
>>
>> Reported-by: Xu Wen <wen.xu@gatech.edu>
>> Signed-off-by: Qu Wenruo <wqu@suse.com>
>> ---
>>  fs/btrfs/relocation.c | 23 ++++++++++++-----------
>>  1 file changed, 12 insertions(+), 11 deletions(-)
>>
>> diff --git a/fs/btrfs/relocation.c b/fs/btrfs/relocation.c
>> index 879b76fa881a..be94c65bb4d2 100644
>> --- a/fs/btrfs/relocation.c
>> +++ b/fs/btrfs/relocation.c
>> @@ -1321,18 +1321,19 @@ static void __del_reloc_root(struct btrfs_root *root)
>>  	struct mapping_node *node = NULL;
>>  	struct reloc_control *rc = fs_info->reloc_ctl;
>>  > -	spin_lock(&rc->reloc_root_tree.lock);
>> -	rb_node = tree_search(&rc->reloc_root_tree.rb_root,
>> -			      root->node->start);
>> -	if (rb_node) {
>> -		node = rb_entry(rb_node, struct mapping_node, rb_node);
>> -		rb_erase(&node->rb_node, &rc->reloc_root_tree.rb_root);
> 
> Just do  if (!rc)
>                 return;
> 
> The function is simple enough, no need to indent multiple lines.

You missed serval lines below, we still have:
---
        spin_lock(&fs_info->trans_lock);
        list_del_init(&root->root_list);
        spin_unlock(&fs_info->trans_lock);
        kfree(node);
---

Which still needs to be called even rc is not initialized.

Thanks,
Qu

>> +	if (rc) {
>> +		spin_lock(&rc->reloc_root_tree.lock);
>> +		rb_node = tree_search(&rc->reloc_root_tree.rb_root,
>> +				      root->node->start);
>> +		if (rb_node) {
>> +			node = rb_entry(rb_node, struct mapping_node, rb_node);
>> +			rb_erase(&node->rb_node, &rc->reloc_root_tree.rb_root);
>> +		}
>> +		spin_unlock(&rc->reloc_root_tree.lock);
>> +		if (!node)
>> +			return;
>> +		BUG_ON((struct btrfs_root *)node->data != root);
>>  	}
>> -	spin_unlock(&rc->reloc_root_tree.lock);
>> -
>> -	if (!node)
>> -		return;
>> -	BUG_ON((struct btrfs_root *)node->data != root);
>>  
>>  	spin_lock(&fs_info->trans_lock);
>>  	list_del_init(&root->root_list);
>>
> --
> 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
> 

  reply	other threads:[~2018-07-02  7:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02  6:25 [PATCH] btrfs: relocation: Only remove reloc rb_trees if reloc control has been initialized Qu Wenruo
2018-07-02  7:31 ` Nikolay Borisov
2018-07-02  7:53   ` Qu Wenruo [this message]
2018-07-02  8:01     ` Nikolay Borisov
2018-07-02  8:05       ` Nikolay Borisov
2018-07-02  8:14       ` Qu Wenruo
2018-07-02 15:58 ` 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=6e41f3cb-9b20-246b-dfc8-ddd5f3ad7441@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