archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <>
To: Ming Lei <>
Cc: "Martin K . Petersen" <>,
Subject: Re: [PATCH 0/4] Revert "Call blk_mq_free_tag_set() earlier"
Date: Mon, 29 Aug 2022 05:14:09 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 8/29/22 02:14, Ming Lei wrote:
> On Mon, Aug 22, 2022 at 6:05 AM Bart Van Assche <> wrote:
>> Since a device, target or host reference may be held when scsi_remove_host()
>> or scsi_remove_target() is called and since te patch series "Call
>> blk_mq_free_tag_set() earlier" makes these functions wait until all references
>> are gone, that patch series may trigger a deadlock. Hence this request to
>> revert the patch series "Call blk_mq_free_tag_set() earlier".
> Care to share the deadlock details? Such as dmesg log or theory behind.

Hi Ming,

Details of two different deadlock scenarios are available here:
* [syzbot] INFO: task hung in scsi_remove_host 
* The link 
[2] in this email includes a call trace and instructions for reproducing 
this issue. My root cause analysis of this deadlock is available here:



  reply	other threads:[~2022-08-29 12:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-21 22:04 [PATCH 0/4] Revert "Call blk_mq_free_tag_set() earlier" Bart Van Assche
2022-08-21 22:04 ` [PATCH 1/4] scsi: core: " Bart Van Assche
2022-08-21 22:05 ` [PATCH 2/4] scsi: core: Revert "Simplify LLD module reference counting" Bart Van Assche
2022-08-21 22:05 ` [PATCH 3/4] scsi: core: Revert "Make sure that hosts outlive targets" Bart Van Assche
2022-08-21 22:05 ` [PATCH 4/4] scsi: core: Revert "Make sure that targets outlive devices" Bart Van Assche
2022-08-29  9:14 ` [PATCH 0/4] Revert "Call blk_mq_free_tag_set() earlier" Ming Lei
2022-08-29 12:14   ` Bart Van Assche [this message]
2022-09-01  5:12 ` Martin K. Petersen

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).