From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <bart.vanassche@sandisk.com>,
Jinpu Wang <jinpu.wang@profitbricks.com>,
linux-block@vger.kernel.org
Subject: Re: [BUG] Deadlock in blk_mq_register_disk error path
Date: Mon, 15 Aug 2016 11:15:34 -0600 [thread overview]
Message-ID: <3a22a49b-9382-710e-028e-f64a9b6f5a27@kernel.dk> (raw)
In-Reply-To: <30d05b8b-7707-a0bf-f55b-65325f55b7d8@sandisk.com>
On 08/15/2016 09:53 AM, Bart Van Assche wrote:
> On 08/02/2016 10:21 AM, Jens Axboe wrote:
>> On 08/02/2016 06:58 AM, Jinpu Wang wrote:
>>> Hi Jens,
>>>
>>> I found in blk_mq_register_disk, we blk_mq_disable_hotplug which in
>>> turn mutex_lock(&all_q_mutex);
>>> queue_for_each_hw_ctx(q, hctx, i) {
>>> ret = blk_mq_register_hctx(hctx);
>>> if (ret)
>>> break; /// if about error out, we will call
>>> unregister below
>>> }
>>>
>>> if (ret)
>>> blk_mq_unregister_disk(disk);
>>>
>>> In blk_mq_unregister_disk, we will try to disable_hotplug again, which
>>> leads to dead lock.
>>>
>>> Did I miss anything?
>>
>> Nope, your analysis looks correct. This should fix it:
>>
>> http://git.kernel.dk/cgit/linux-block/commit/?h=for-linus&id=6316338a94b2319abe9d3790eb9cdc56ef81ac1a
>
> Hi Jens,
>
> Will that patch be included in stable kernels? I just encountered a
> deadlock with kernel v4.7 that looks similar.
Sure, we can push to stable, it's a pretty straight forward patch. Can
you reproduce at will? Would be nice to know if it hit the error case,
which is where it would hang.
--
Jens Axboe
next prev parent reply other threads:[~2016-08-15 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 13:58 [BUG] Deadlock in blk_mq_register_disk error path Jinpu Wang
2016-08-02 17:21 ` Jens Axboe
2016-08-03 8:02 ` Jinpu Wang
2016-08-15 15:53 ` Bart Van Assche
2016-08-15 16:01 ` Jinpu Wang
2016-08-15 16:22 ` Bart Van Assche
2016-08-16 8:18 ` Jinpu Wang
2016-08-15 17:15 ` Jens Axboe [this message]
2016-08-15 17:41 ` Bart Van Assche
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=3a22a49b-9382-710e-028e-f64a9b6f5a27@kernel.dk \
--to=axboe@kernel.dk \
--cc=bart.vanassche@sandisk.com \
--cc=jinpu.wang@profitbricks.com \
--cc=linux-block@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