From: "yukuai (C)" <yukuai3@huawei.com>
To: <axboe@kernel.dk>
Cc: <linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yi.zhang@huawei.com>
Subject: Re: [PATCH] block: don't decrement flush request refcount if it's state is idle in flush_end_io()
Date: Fri, 13 Aug 2021 17:40:18 +0800 [thread overview]
Message-ID: <e251976b-eab8-1c79-0891-25d48b31d4db@huawei.com> (raw)
In-Reply-To: <20210808070330.763177-1-yukuai3@huawei.com>
Hi, jens
Can you please consider to apply this patch?
Thanks
Kuai
On 2021/08/08 15:03, Yu Kuai wrote:
> flush_end_io() currently decrement request refcount unconditionally.
> However, it's possible that the request is already idle and it's
> refcount is zero since that flush_end_io() can be called concurrently.
>
> For example, nbd_clear_que() can be called concurrently with normal
> io completion or io timeout.
>
> Thus check idle before decrement to avoid refcount_t underflow
> warning.
>
> Signed-off-by: Yu Kuai <yukuai3@huawei.com>
> ---
> block/blk-flush.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/block/blk-flush.c b/block/blk-flush.c
> index 1002f6c58181..9b65dc43702c 100644
> --- a/block/blk-flush.c
> +++ b/block/blk-flush.c
> @@ -222,7 +222,8 @@ static void flush_end_io(struct request *flush_rq, blk_status_t error)
> /* release the tag's ownership to the req cloned from */
> spin_lock_irqsave(&fq->mq_flush_lock, flags);
>
> - if (!refcount_dec_and_test(&flush_rq->ref)) {
> + if (blk_mq_rq_state(flush_rq) == MQ_RQ_IDLE ||
> + !refcount_dec_and_test(&flush_rq->ref)) {
> fq->rq_status = error;
> spin_unlock_irqrestore(&fq->mq_flush_lock, flags);
> return;
>
next prev parent reply other threads:[~2021-08-13 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 7:03 [PATCH] block: don't decrement flush request refcount if it's state is idle in flush_end_io() Yu Kuai
2021-08-08 8:44 ` Ming Lei
2021-08-13 9:40 ` yukuai (C) [this message]
2021-08-13 12:34 ` yukuai (C)
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=e251976b-eab8-1c79-0891-25d48b31d4db@huawei.com \
--to=yukuai3@huawei.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yi.zhang@huawei.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