From: "jianchao.wang" <jianchao.w.wang@oracle.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
James Bottomley <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-block <linux-block@vger.kernel.org>,
Linux SCSI List <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] block: export __blk_complete_request
Date: Fri, 15 Jun 2018 11:26:03 +0800 [thread overview]
Message-ID: <7a77829a-ba5f-8975-edb0-ffdf25dc71d6@oracle.com> (raw)
In-Reply-To: <CACVXFVMPAdFbX3x-KUjHCQhb_rT6p9ROYHg63aUtEqdbitEaKQ@mail.gmail.com>
Hi Ming
On 06/15/2018 11:20 AM, Ming Lei wrote:
> On Fri, Jun 15, 2018 at 11:04 AM, jianchao.wang
> <jianchao.w.wang@oracle.com> wrote:
>> Hi Ming
>>
>> Thanks for your kindly response.
>>
>> On 06/15/2018 10:56 AM, Ming Lei wrote:
>>>>> IMO, ref-counter is just to fix the blk-mq req life recycle issue.
>>>>> It cannot replace the blk_mark_rq_complete which could avoid the race between
>>>>> timeout and io completion path.
>>>> The .timeout return BLK_EH_DONE doesn't always mean the request has been completed.
>>>> Such as scsi-mid layer, its .timeout callback return BLK_EH_DONE but the timed out
>>>> request is still in abort or eh process. What if a completion irq come during that ?
>>> For blk-mq, it is avoided by the atomic state change in
>>> __blk_mq_complete_request(),
>>> that is why I mentioned the question in my last reply.
>>>
>>
>> but blk_mq_check_expired doesn't do that.
>> do I miss anything ?
>
> Right, that is the difference between blk-mq and legacy now,
Sorry, I cannot follow your point.
blk_mq_check_expired doesn't do a atmoc state change from IN-FLIGHT to COMPLETE.
__blk_mq_complete_request could still proceed to complete a timed out request
which is in scsi abort or eh process. Is it really OK ?
Thanks
Jianchao
> then if scsi-mq
> drivers can work well, they should work well with the following change in the
> non-mq mode:
>
> diff --git a/block/blk-timeout.c b/block/blk-timeout.c
> index 4b8a48d48ba1..9fce09d55652 100644
> --- a/block/blk-timeout.c
> +++ b/block/blk-timeout.c
> @@ -88,7 +88,6 @@ static void blk_rq_timed_out(struct request *req)
> switch (ret) {
> case BLK_EH_RESET_TIMER:
> blk_add_timer(req);
> - blk_clear_rq_complete(req);
> break;
> case BLK_EH_DONE:
> /*
> @@ -115,8 +114,7 @@ static void blk_rq_check_expired(struct request
> *rq, unsigned long *next_timeout
> /*
> * Check if we raced with end io completion
> */
> - if (!blk_mark_rq_complete(rq))
> - blk_rq_timed_out(rq);
> + blk_rq_timed_out(rq);
> } else if (!*next_set || time_after(*next_timeout, deadline)) {
> *next_timeout = deadline;
> *next_set = 1;
>
>
> Thanks,
> Ming Lei
>
next prev parent reply other threads:[~2018-06-15 3:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 1:57 [PATCH 1/2] block: export __blk_complete_request Jianchao Wang
2018-06-15 1:57 ` [PATCH 2/2] scsi_transport_fc: use __blk_complete_request in fc_bsg_job_timeout Jianchao Wang
2018-06-15 2:17 ` [PATCH 1/2] block: export __blk_complete_request Ming Lei
2018-06-15 2:22 ` jianchao.wang
2018-06-15 2:44 ` jianchao.wang
2018-06-15 2:56 ` Ming Lei
2018-06-15 3:04 ` jianchao.wang
2018-06-15 3:20 ` Ming Lei
2018-06-15 3:26 ` jianchao.wang [this message]
2018-06-15 4:03 ` Ming Lei
2018-06-15 5:10 ` jianchao.wang
2018-06-15 11:58 ` Christoph Hellwig
2018-06-15 2:49 ` Ming Lei
2018-06-19 14:09 ` Christoph Hellwig
2018-06-19 14:52 ` jianchao.wang
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=7a77829a-ba5f-8975-edb0-ffdf25dc71d6@oracle.com \
--to=jianchao.w.wang@oracle.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tom.leiming@gmail.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