From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Akinobu Mita <akinobu.mita@gmail.com>, linux-block@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] null_blk: execute complete callback for fake timeout request
Date: Mon, 13 Mar 2023 10:00:30 +0900 [thread overview]
Message-ID: <49cfce8b-042e-7248-928f-4a5c5f7d0e31@opensource.wdc.com> (raw)
In-Reply-To: <20230312123556.12298-1-akinobu.mita@gmail.com>
On 3/12/23 21:35, Akinobu Mita wrote:
> When injecting a fake timeout into the null_blk driver by fail_io_timeout,
> the request timeout handler doen't execute blk_mq_complete_request(), so
> the complete callback will never be executed for that timed out request.
>
> The null_blk driver also has a driver-specific fake timeout mechanism and
> does not have the problem that occur when using the generic one.
> Fix the problem by doing similar to what the driver-specific one does.
>
> Fixes: de3510e52b0a ("null_blk: fix command timeout completion handling")
> Cc: Damien Le Moal <damien.lemoal@wdc.com>
> Cc: Jens Axboe <axboe@kernel.dk>
> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
> ---
> drivers/block/null_blk/main.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/block/null_blk/main.c b/drivers/block/null_blk/main.c
> index 4c601ca9552a..69250b3cfecd 100644
> --- a/drivers/block/null_blk/main.c
> +++ b/drivers/block/null_blk/main.c
> @@ -1413,7 +1413,9 @@ static inline void nullb_complete_cmd(struct nullb_cmd *cmd)
> case NULL_IRQ_SOFTIRQ:
> switch (cmd->nq->dev->queue_mode) {
> case NULL_Q_MQ:
> - if (likely(!blk_should_fake_timeout(cmd->rq->q)))
> + if (unlikely(blk_should_fake_timeout(cmd->rq->q)))
> + cmd->fake_timeout = true;
> + else
> blk_mq_complete_request(cmd->rq);
> break;
> case NULL_Q_BIO:
I have not checked, but does this work ?
diff --git a/drivers/block/null_blk/main.c b/drivers/block/null_blk/main.c
index 4c601ca9552a..52d689aa3171 100644
--- a/drivers/block/null_blk/main.c
+++ b/drivers/block/null_blk/main.c
@@ -1413,7 +1413,7 @@ static inline void nullb_complete_cmd(struct nullb_cmd *cmd)
case NULL_IRQ_SOFTIRQ:
switch (cmd->nq->dev->queue_mode) {
case NULL_Q_MQ:
- if (likely(!blk_should_fake_timeout(cmd->rq->q)))
+ if (!cmd->fake_timeout)
blk_mq_complete_request(cmd->rq);
break;
case NULL_Q_BIO:
@@ -1675,7 +1675,8 @@ static blk_status_t null_queue_rq(struct blk_mq_hw_ctx *hctx,
cmd->rq = bd->rq;
cmd->error = BLK_STS_OK;
cmd->nq = nq;
- cmd->fake_timeout = should_timeout_request(bd->rq);
+ cmd->fake_timeout = should_timeout_request(bd->rq) ||
+ blk_should_fake_timeout(bd->rq->q);
blk_mq_start_request(bd->rq);
It is I think cleaner as it unifies the internal fake timeout and
blk_should_fake_timeout().
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2023-03-13 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 12:35 [PATCH] null_blk: execute complete callback for fake timeout request Akinobu Mita
2023-03-13 1:00 ` Damien Le Moal [this message]
2023-03-13 16:39 ` Akinobu Mita
2023-03-13 16:50 ` Keith Busch
2023-03-14 3:56 ` Damien Le Moal
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=49cfce8b-042e-7248-928f-4a5c5f7d0e31@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=akinobu.mita@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@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