From: Bart Van Assche <bvanassche@acm.org>
To: "Martin K . Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH 0/4] Revert "Call blk_mq_free_tag_set() earlier"
Date: Sun, 21 Aug 2022 15:04:58 -0700 [thread overview]
Message-ID: <20220821220502.13685-1-bvanassche@acm.org> (raw)
Hi Martin,
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".
Thanks,
Bart.
Bart Van Assche (4):
scsi: core: Revert "Call blk_mq_free_tag_set() earlier"
scsi: core: Revert "Simplify LLD module reference counting"
scsi: core: Revert "Make sure that hosts outlive targets"
scsi: core: Revert "Make sure that targets outlive devices"
drivers/scsi/hosts.c | 18 +++++-------------
drivers/scsi/scsi.c | 9 +++------
drivers/scsi/scsi_scan.c | 9 ---------
drivers/scsi/scsi_sysfs.c | 29 ++++++++++++-----------------
include/scsi/scsi_device.h | 2 --
include/scsi/scsi_host.h | 3 ---
6 files changed, 20 insertions(+), 50 deletions(-)
next reply other threads:[~2022-08-21 22:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 22:04 Bart Van Assche [this message]
2022-08-21 22:04 ` [PATCH 1/4] scsi: core: Revert "Call blk_mq_free_tag_set() earlier" 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
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:
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=20220821220502.13685-1-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).