linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Anand Jain <anand.jain@oracle.com>, linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz
Subject: Re: [PATCH 2/3] btrfs: cleanup btrfs_init_new_device()
Date: Mon, 25 Sep 2017 16:09:35 +0300	[thread overview]
Message-ID: <bbd6b15b-146a-9373-7242-f69a69bd0c4f@suse.com> (raw)
In-Reply-To: <6af9ec03-712a-d78e-6ad5-f4aff0f0dd61@suse.com>



On 25.09.2017 16:07, Nikolay Borisov wrote:
> 
> 
> On 25.09.2017 15:31, Anand Jain wrote:
>> Moves btrfs_abort_transaction() to the error goto and renames
>> error_trans to error_sysfs. This is a preparatory patch to
>> remove the BUG_ON() in btrfs_init_new_device().
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>>  fs/btrfs/volumes.c | 23 +++++++++--------------
>>  1 file changed, 9 insertions(+), 14 deletions(-)
>>
>> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
>> index 9d64700cc9b6..5c34eea9d12d 100644
>> --- a/fs/btrfs/volumes.c
>> +++ b/fs/btrfs/volumes.c
>> @@ -2443,26 +2443,20 @@ int btrfs_init_new_device(struct btrfs_fs_info *fs_info, const char *device_path
>>  		mutex_lock(&fs_info->chunk_mutex);
>>  		ret = init_first_rw_device(trans, fs_info);
>>  		mutex_unlock(&fs_info->chunk_mutex);
>> -		if (ret) {
>> -			btrfs_abort_transaction(trans, ret);
>> -			goto error_trans;
>> -		}
>> +		if (ret)
>> +			goto error_sysfs;
>>  	}
>>  
>>  	ret = btrfs_add_device(trans, fs_info, device);
>> -	if (ret) {
>> -		btrfs_abort_transaction(trans, ret);
>> -		goto error_trans;
>> -	}
>> +	if (ret)
>> +		goto error_sysfs;
>>  
>>  	if (seeding_dev) {
>>  		char fsid_buf[BTRFS_UUID_UNPARSED_SIZE];
>>  
>>  		ret = btrfs_finish_sprout(trans, fs_info);
>> -		if (ret) {
>> -			btrfs_abort_transaction(trans, ret);
>> -			goto error_trans;
>> -		}
>> +		if (ret)
>> +			goto error_sysfs;
>>  
>>  		/* Sprouting would change fsid of the mounted root,
>>  		 * so rename the fsid on the sysfs
>> @@ -2500,12 +2494,13 @@ int btrfs_init_new_device(struct btrfs_fs_info *fs_info, const char *device_path
>>  	update_dev_time(device_path);
>>  	return ret;
>>  
>> -error_trans:
>> +error_sysfs:
>> +	btrfs_sysfs_rm_device_link(fs_info->fs_devices, device);
> 
> Any reason why you move btrfs_sysfs_rm_device_link?
> 
>>  	if (seeding_dev)
>>  		sb->s_flags |= MS_RDONL> +	btrfs_abort_transaction(trans, ret);
>>  	btrfs_end_transaction(trans);
>>  	rcu_string_free(device->name);
>> -	btrfs_sysfs_rm_device_link(fs_info->fs_devices, device);
>>  	kfree(device);>  error:
>>  	blkdev_put(bdev, FMODE_EXCL);
> 
> Also which branch is your code based on since in Linus' master the error
> handling (before your patch) looks a bit different. E.g. the MS_RDONL
> stuff look wrong.
> 
> error_trans:
> 
>         btrfs_end_transaction(trans);
> 
>         rcu_string_free(device->name);
> 
>         btrfs_sysfs_rm_device_link(fs_info->fs_devices, device);
> 
>         kfree(device);
> 
> error:
> 
>         blkdev_put(bdev, FMODE_EXCL);
> 
>         if (seeding_dev) {
> 
>                 mutex_unlock(&uuid_mutex);
> 
>                 up_write(&sb->s_umount);
> 
>         }
> 
>         return ret;

Ok, turned out I hadn't received 1/3 so this answers this question. The
sysfs rm stands though


> 
>>

  reply	other threads:[~2017-09-25 13:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 12:31 [PATCH 0/3] fix bug in btrfs_init_new_device() Anand Jain
2017-09-25 12:31 ` [PATCH 1/3] btrfs: undo writable when sprouting fails Anand Jain
2017-09-25 13:03   ` Qu Wenruo
2017-09-25 14:52   ` David Sterba
2017-09-25 12:31 ` [PATCH 2/3] btrfs: cleanup btrfs_init_new_device() Anand Jain
2017-09-25 13:07   ` Nikolay Borisov
2017-09-25 13:09     ` Nikolay Borisov [this message]
2017-09-26  7:57       ` Anand Jain
2017-09-26  8:00         ` Anand Jain
2017-09-26  8:07         ` Nikolay Borisov
2017-09-26  8:45           ` Anand Jain
2017-09-25 13:08   ` Qu Wenruo
2017-09-25 14:56   ` David Sterba
2017-09-25 12:31 ` [PATCH 3/3] btrfs: fix BUG_ON in btrfs_init_new_device() Anand Jain
2017-09-26  7:48 ` [PATCH v2 0/3] fix bug " Anand Jain
2017-09-26  7:48   ` [PATCH v2 1/3] btrfs: undo writable when sprouting fails Anand Jain
2017-09-26  7:48   ` [PATCH v2 2/3] btrfs: cleanup btrfs_init_new_device() Anand Jain
2017-09-26  7:48   ` [PATCH v2 3/3] btrfs: fix BUG_ON in btrfs_init_new_device() 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=bbd6b15b-146a-9373-7242-f69a69bd0c4f@suse.com \
    --to=nborisov@suse.com \
    --cc=anand.jain@oracle.com \
    --cc=dsterba@suse.cz \
    --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).