From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <keith.busch@intel.com>,
linux-scsi@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH 1/2] scsi: Do not rely on blk-mq for double completions
Date: Tue, 13 Nov 2018 12:20:46 -0700 [thread overview]
Message-ID: <b2d9c646-3311-9f85-6e8b-de3ddf295899@kernel.dk> (raw)
In-Reply-To: <20181113185712.10063-1-keith.busch@intel.com>
On 11/13/18 11:57 AM, Keith Busch wrote:
> The scsi timeout error handling had been directly updating the request
> state to prevent a natural completion and error handling from completing
> the same request twice. Fix this layering violation by having scsi
> control the fate of its commands with scsi owned flags rather than
> use blk-mq's.
>
> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
> index 61babcb269ab..c680171ca201 100644
> --- a/drivers/scsi/scsi_lib.c
> +++ b/drivers/scsi/scsi_lib.c
> @@ -1635,8 +1635,18 @@ static blk_status_t scsi_mq_prep_fn(struct request *req)
>
> static void scsi_mq_done(struct scsi_cmnd *cmd)
> {
> + if (test_and_set_bit(__SCMD_COMPLETE, &cmd->flags))
> + return;
> trace_scsi_dispatch_cmd_done(cmd);
> blk_mq_complete_request(cmd->request);
> +
> +#ifdef CONFIG_FAIL_IO_TIMEOUT
> + /*
> + * Clearing complete here serves only to allow the desired recovery to
> + * escalate on blk_rq_should_fake_timeout()'s error injection.
> + */
> + clear_bit(__SCMD_COMPLETE, &cmd->flags);
> +#endif
> }
We could have this be:
static void scsi_mq_done(struct scsi_cmnd *cmd)
{
if (test_and_set_bit(__SCMD_COMPLETE, &cmd->flags))
return;
trace_scsi_dispatch_cmd_done(cmd);
if (blk_mq_complete_request(cmd->request)) {
/*
* Clearing complete here serves only to allow the
* desired recovery to escalate on
* blk_rq_should_fake_timeout()'s error injection.
*/
clear_bit(__SCMD_COMPLETE, &cmd->flags);
}
}
with
bool blk_mq_complete_request(struct request *rq)
{
if (unlikely(blk_should_fake_timeout(rq->q)))
return true;
__blk_mq_complete_request(rq);
return false;
}
and not have this CONFIG_FAIL_IO_TIMEOUT dependency, but that'd be a bit
more expensive.
Was going to suggest a request flag, but the request is gone at this
point. So that won't really work...
I'm with your solution as well, fwiw.
--
Jens Axboe
next prev parent reply other threads:[~2018-11-13 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 18:57 [PATCH 1/2] scsi: Do not rely on blk-mq for double completions Keith Busch
2018-11-13 18:57 ` [PATCH 2/2] blk-mq: Simplify request completion state Keith Busch
2018-11-13 19:20 ` Jens Axboe [this message]
2018-11-13 19:45 ` [PATCH 1/2] scsi: Do not rely on blk-mq for double completions Keith Busch
2018-11-14 4:35 ` Jens Axboe
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=b2d9c646-3311-9f85-6e8b-de3ddf295899@kernel.dk \
--to=axboe@kernel.dk \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@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