From: Jens Axboe <axboe@kernel.dk>
To: Yufen Yu <yuyufen@huawei.com>
Cc: linux-block@vger.kernel.org, hch@lst.de, ming.lei@redhat.com,
bvanassche@acm.org, kbusch@kernel.org
Subject: Re: [PATCH] block: only update parent bi_status when bio fail
Date: Wed, 31 Mar 2021 19:18:23 -0600 [thread overview]
Message-ID: <3afcc0a1-d01b-5007-2621-231e7d8143e9@kernel.dk> (raw)
In-Reply-To: <20210331115359.1125679-1-yuyufen@huawei.com>
On 3/31/21 5:53 AM, Yufen Yu wrote:
> For multiple split bios, if one of the bio is fail, the whole
> should return error to application. But we found there is a race
> between bio_integrity_verify_fn and bio complete, which return
> io success to application after one of the bio fail. The race as
> following:
>
> split bio(READ) kworker
>
> nvme_complete_rq
> blk_update_request //split error=0
> bio_endio
> bio_integrity_endio
> queue_work(kintegrityd_wq, &bip->bip_work);
>
> bio_integrity_verify_fn
> bio_endio //split bio
> __bio_chain_endio
> if (!parent->bi_status)
>
> <interrupt entry>
> nvme_irq
> blk_update_request //parent error=7
> req_bio_endio
> bio->bi_status = 7 //parent bio
> <interrupt exit>
>
> parent->bi_status = 0
> parent->bi_end_io() // return bi_status=0
>
> The bio has been split as two: split and parent. When split
> bio completed, it depends on kworker to do endio, while
> bio_integrity_verify_fn have been interrupted by parent bio
> complete irq handler. Then, parent bio->bi_status which have
> been set in irq handler will overwrite by kworker.
>
> In fact, even without the above race, we also need to conside
> the concurrency beteen mulitple split bio complete and update
> the same parent bi_status. Normally, multiple split bios will
> be issued to the same hctx and complete from the same irq
> vector. But if we have updated queue map between multiple split
> bios, these bios may complete on different hw queue and different
> irq vector. Then the concurrency update parent bi_status may
> cause the final status error.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-04-01 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 11:53 [PATCH] block: only update parent bi_status when bio fail Yufen Yu
2021-04-01 0:54 ` Ming Lei
2021-04-01 1:18 ` Jens Axboe [this message]
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=3afcc0a1-d01b-5007-2621-231e7d8143e9@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=yuyufen@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;
as well as URLs for NNTP newsgroup(s).