Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: "Martin K . Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, John Garry <john.g.garry@oracle.com>,
	Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH v2 0/2] Call scsi_host_busy() after the SCSI host has been added
Date: Fri,  9 Jan 2026 12:51:00 -0800	[thread overview]
Message-ID: <20260109205104.496478-1-bvanassche@acm.org> (raw)

Hi Martin,

The UFS driver is the only SCSI driver I know of that may call
scsi_host_busy() before the SCSI host has been added. This patch series
modifies the UFS driver such that scsi_host_busy() is only called after the
SCSI host has been added. Additionally, commit a0b7780602b1 ("scsi: core:
Fix a regression triggered by scsi_host_busy()") is reverted because all
scsi_host_busy() calls now happen after the corresponding SCSI host has
been added.

Please consider this patch series for the next merge window.

Thanks,

Bart.

Changes compared to v1:
 - Removed the WARN_ON_ONCE(!shost->tag_set.ops); statement from patch 2/2.

Bart Van Assche (2):
  ufs: core: Only call scsi_host_busy() after the SCSI host has been
    added
  scsi: core: Revert "Fix a regression triggered by scsi_host_busy()"

 drivers/scsi/hosts.c      | 5 ++---
 drivers/ufs/core/ufshcd.c | 6 ++++--
 2 files changed, 6 insertions(+), 5 deletions(-)


             reply	other threads:[~2026-01-09 20:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09 20:51 Bart Van Assche [this message]
2026-01-09 20:51 ` [PATCH v2 1/2] ufs: core: Only call scsi_host_busy() after the SCSI host has been added Bart Van Assche
2026-01-13  7:25   ` Peter Wang (王信友)
2026-01-09 20:51 ` [PATCH v2 2/2] scsi: core: Revert "Fix a regression triggered by scsi_host_busy()" Bart Van Assche
2026-01-10  8:01   ` John Garry
2026-01-12  3:08 ` [PATCH v2 0/2] Call scsi_host_busy() after the SCSI host has been added Martin K. Petersen
2026-01-17  4:36 ` 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=20260109205104.496478-1-bvanassche@acm.org \
    --to=bvanassche@acm.org \
    --cc=john.g.garry@oracle.com \
    --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