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,
	yauhen.kharuzhy@zavadatar.com
Subject: Re: [PATCH] btrfs: fix lock dep warning, move scratch dev out of device_list_mutex and uuid_mutex
Date: Mon, 2 May 2016 07:12:39 +0800	[thread overview]
Message-ID: <57268D67.9010200@oracle.com> (raw)
In-Reply-To: <20160425150908.GB29353@twin.jikos.cz>



On 04/25/2016 11:09 PM, David Sterba wrote:
> On Mon, Apr 18, 2016 at 04:51:23PM +0800, Anand Jain wrote:
>> When the replace target fails, the target device will be taken
>> out of fs device list, scratch + update_dev_time and freed. However
>> we could do the scratch  + update_dev_time and free part after the
>> device has been taken out of device list, so that we don't have to
>> hold the device_list_mutex and uuid_mutex locks.
>>
>> Reported issue:
> [...]
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> Reported-by: Yauhen Kharuzhy <yauhen.kharuzhy@zavadatar.com>
>
> Reviewed-by: David Sterba <dsterba@suse.com>

Thanks.
Anand

> --
> 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:[~2016-05-01 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18  8:51 [PATCH] btrfs: fix lock dep warning, move scratch dev out of device_list_mutex and uuid_mutex Anand Jain
2016-04-25 15:09 ` David Sterba
2016-05-01 23:12   ` Anand Jain [this message]

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=57268D67.9010200@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=yauhen.kharuzhy@zavadatar.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;
as well as URLs for NNTP newsgroup(s).