From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>,
Keith Busch <keith.busch@intel.com>
Cc: linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
Martin Petersen <martin.petersen@oracle.com>,
Bart Van Assche <bvanassche@acm.org>
Subject: Re: [PATCHv3 2/3] scsi: Do not rely on blk-mq for double completions
Date: Mon, 19 Nov 2018 08:17:38 -0700 [thread overview]
Message-ID: <fbd6800f-e3c2-a8cd-7f20-fb448a8b71d1@kernel.dk> (raw)
In-Reply-To: <20181119085815.GB29626@infradead.org>
On 11/19/18 1:58 AM, Christoph Hellwig wrote:
>> index 5d83a162d03b..c1d5e4e36125 100644
>> --- a/drivers/scsi/scsi_lib.c
>> +++ b/drivers/scsi/scsi_lib.c
>> @@ -1635,8 +1635,11 @@ static blk_status_t scsi_mq_prep_fn(struct request *req)
>>
>> static void scsi_mq_done(struct scsi_cmnd *cmd)
>> {
>> + if (unlikely(test_and_set_bit(__SCMD_COMPLETE, &cmd->flags)))
>> + return;
>> trace_scsi_dispatch_cmd_done(cmd);
>> - blk_mq_complete_request(cmd->request);
>> + if (unlikely(!blk_mq_complete_request(cmd->request)))
>> + clear_bit(__SCMD_COMPLETE, &cmd->flags);
>> }
>
> This looks a little odd to me. If we didn't complete the command
> someone else did. Why would we clear the bit in this case?
It's strictly for the fake timeout, it didn't complete it, it just
ignored it. This is an artifact of the weird way that works.
--
Jens Axboe
next prev parent reply other threads:[~2018-11-19 15:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 17:58 [PATCHv3 0/3] scsi timeout handling updates Keith Busch
2018-11-15 17:58 ` [PATCHv3 1/3] blk-mq: Return true if request was completed Keith Busch
2018-11-19 8:31 ` Christoph Hellwig
2018-11-15 17:58 ` [PATCHv3 2/3] scsi: Do not rely on blk-mq for double completions Keith Busch
2018-11-16 9:53 ` Hannes Reinecke
2018-11-16 14:46 ` Bart Van Assche
2018-11-19 8:58 ` Christoph Hellwig
2018-11-19 15:17 ` Jens Axboe [this message]
2018-11-19 15:19 ` Keith Busch
2018-11-21 13:12 ` Christoph Hellwig
2018-11-26 15:32 ` Jens Axboe
2018-11-26 15:31 ` Keith Busch
2018-11-15 17:58 ` [PATCHv3 3/3] blk-mq: Simplify request completion state Keith Busch
2018-11-19 8:58 ` Christoph Hellwig
2018-11-15 19:53 ` [PATCHv3 0/3] scsi timeout handling updates 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=fbd6800f-e3c2-a8cd-7f20-fb448a8b71d1@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@infradead.org \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.