From: Bart Van Assche <bvanassche@acm.org>
To: Hannes Reinecke <hare@suse.de>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: allow state transitions BLOCK -> BLOCK
Date: Fri, 17 Jul 2020 19:51:47 -0700 [thread overview]
Message-ID: <68eb8671-e8ea-4a52-0679-f7c4e0c0ee3b@acm.org> (raw)
In-Reply-To: <b31a9be0-1e42-f49f-d5e7-e4568dafa8b2@suse.de>
On 2020-07-12 23:19, Hannes Reinecke wrote:
> I think this should be sufficient:
>
> diff --git a/drivers/scsi/scsi_transport_srp.c
> b/drivers/scsi/scsi_transport_srp.c
> index d4d1104fac99..180b323f46b8 100644
> --- a/drivers/scsi/scsi_transport_srp.c
> +++ b/drivers/scsi/scsi_transport_srp.c
> @@ -404,11 +404,6 @@ static void __rport_fail_io_fast(struct srp_rport
> *rport)
>
> if (srp_rport_set_state(rport, SRP_RPORT_FAIL_FAST))
> return;
> - /*
> - * Call scsi_target_block() to wait for ongoing
> shost->queuecommand()
> - * calls before invoking i->f->terminate_rport_io().
> - */
> - scsi_target_block(rport->dev.parent);
> scsi_target_unblock(rport->dev.parent, SDEV_TRANSPORT_OFFLINE);
>
> /* Involve the LLD if possible to terminate all I/O on the
> rport. */
> @@ -570,8 +565,6 @@ int srp_reconnect_rport(struct srp_rport *rport)
> * failure timers if these had not yet been started.
> */
> __rport_fail_io_fast(rport);
> - scsi_target_unblock(&shost->shost_gendev,
> - SDEV_TRANSPORT_OFFLINE);
> __srp_start_tl_fail_timers(rport);
> } else if (rport->state != SRP_RPORT_BLOCKED) {
> scsi_target_unblock(&shost->shost_gendev,
Adding a comment like this above __rport_fail_io_fast() would be welcome:
/*
* scsi_target_block() must have been called before this function is
* called to guarantee that no .queuecommand() calls are in progress.
*/
Otherwise the above patch looks fine to me.
Bart.
prev parent reply other threads:[~2020-07-18 2:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 14:24 [PATCH] scsi: allow state transitions BLOCK -> BLOCK Hannes Reinecke
2020-07-02 14:34 ` James Bottomley
2020-07-02 15:14 ` Hannes Reinecke
2020-07-02 17:23 ` Bart Van Assche
2020-07-03 5:30 ` Hannes Reinecke
2020-07-06 2:30 ` Bart Van Assche
2020-07-06 6:22 ` Hannes Reinecke
2020-07-12 4:13 ` Bart Van Assche
2020-07-13 6:19 ` Hannes Reinecke
2020-07-18 2:51 ` Bart Van Assche [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=68eb8671-e8ea-4a52-0679-f7c4e0c0ee3b@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--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