linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v4 1/2] btrfs: add function to device list delete
Date: Wed, 6 Dec 2017 05:30:43 +0800	[thread overview]
Message-ID: <fd040d83-f7c7-4069-81e7-697d6e757db2@oracle.com> (raw)
In-Reply-To: <20171205190616.GU3553@twin.jikos.cz>



On 12/06/2017 03:06 AM, David Sterba wrote:
> On Tue, Dec 05, 2017 at 04:52:56PM +0800, Anand Jain wrote:
>> We need device delete from the dev_list so create a new function.
>> New instead of refactor of btrfs_free_stale_device() because,
>> btrfs_free_stale_device() doesn't hold device_list_mutex which
>> is actually needed here.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>> v1: title of this patch
>>    btrfs: refactor btrfs_free_stale_device() to get device list delete
>> v2:
>>   delete_device_from_list() is not pealed from btrfs_free_stale_device()
>>   as this needs device_list_mutex. And its static now.
>> v3: Send to correct ML
>> v4: no change
>>
>>   fs/btrfs/volumes.c | 22 ++++++++++++++++++++++
>>   1 file changed, 22 insertions(+)
>>
>> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
>> index 04164337ac69..5deda80316f0 100644
>> --- a/fs/btrfs/volumes.c
>> +++ b/fs/btrfs/volumes.c
>> @@ -531,6 +531,28 @@ static void pending_bios_fn(struct btrfs_work *work)
>>   	run_scheduled_bios(device);
>>   }
>>   
>> +static void delete_device_from_list(struct btrfs_device *device)
>> +{
>> +	struct btrfs_fs_devices *fs_devices;
>> +
>> +	fs_devices = device->fs_devices;
>> +
>> +	lockdep_assert_held(&uuid_mutex);
>> +
>> +	mutex_lock(&fs_devices->device_list_mutex);
>> +	fs_devices->num_devices--;
>> +	list_del(&device->dev_list);
>> +	mutex_unlock(&fs_devices->device_list_mutex);
>> +
>> +	rcu_string_free(device->name);
>> +	kfree(device);
> 
> Please use the new helper introduced in patch "btrfs: introduce
> free_device helper" (currently in misc-next), you'd leak the flush bio
> here.

   Ok. Will do.

Thanks, Anand

>> +
>> +	if (fs_devices->num_devices == 0) {
>> +		btrfs_sysfs_remove_fsid(fs_devices);
>> +		list_del(&fs_devices->list);
>> +		free_fs_devices(fs_devices);
>> +	}
>> +}
> --
> 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:[~2017-12-05 21:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05  8:52 [PATCH v4 0/2] Add cli and ioctl to ignore a scanned device Anand Jain
2017-12-05  8:52 ` [PATCH v4 1/2] btrfs: add function to device list delete Anand Jain
2017-12-05 19:06   ` David Sterba
2017-12-05 21:30     ` Anand Jain [this message]
2017-12-05  8:52 ` [PATCH v4] btrfs-progs: add 'btrfs device ignore' cli Anand Jain
2017-12-05 19:11   ` David Sterba
2017-12-06  7:26     ` Anand Jain
2017-12-05  8:52 ` [PATCH v4 2/2] btrfs: introduce feature to ignore a btrfs device Anand Jain
2017-12-05 19:24   ` David Sterba
2017-12-06  7:55     ` 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=fd040d83-f7c7-4069-81e7-697d6e757db2@oracle.com \
    --to=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).