From: Christoph Hellwig <[email protected]>
To: Bijan Mottahedeh <[email protected]>
Cc: Christoph Hellwig <[email protected]>,
[email protected], [email protected],
[email protected]
Subject: Re: [PATCH 1/1] block: Manage bio references so the bio persists until necessary
Date: Mon, 3 Feb 2020 00:34:22 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Fri, Jan 31, 2020 at 06:08:16PM +0000, Bijan Mottahedeh wrote:
> I think the problem is that in the async case, bio_get() is not called for
> the initial bio *before* the submit_bio() call for that bio:
>
> if (dio->is_sync) {
> dio->waiter = current;
> bio_get(bio);
> } else {
> dio->iocb = iocb;
> }
>
>
> The bio_get() call for the async case happens too late, after the
> submit_bio() call:
>
> if (!dio->multi_bio) {
> /*
> * AIO needs an extra reference to ensure the dio
> * structure which is embedded into the first bio
> * stays around.
> */
> if (!is_sync)
> bio_get(bio);
> dio->multi_bio = true;
> atomic_set(&dio->ref, 2);
> } else {
> atomic_inc(&dio->ref);
> }
That actualy is before the submit_bio call, which is just below that
code.
>
>
> See my previous message on the mailing list titled "io_uring: acquire
> ctx->uring_lock before calling io_issue_sqe()" for the more details but
> basically blkdev_bio_end_io() can be called before submit_bio() returns and
> therefore free the initial bio. I think it is the unconditional bio_put()
> at the end that does it.
But we never access the bio after submit_bio returns for the single
bio async case, so I still don't understand the problem.
next prev parent reply other threads:[~2020-02-03 8:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 3:23 [PATCH 0/1] block: Manage bio references so the bio persists until necessary Bijan Mottahedeh
2020-01-31 3:23 ` [PATCH 1/1] " Bijan Mottahedeh
2020-01-31 6:42 ` Christoph Hellwig
2020-01-31 18:08 ` Bijan Mottahedeh
2020-02-03 8:34 ` Christoph Hellwig [this message]
2020-02-03 21:07 ` Bijan Mottahedeh
2020-02-04 7:51 ` Christoph Hellwig
2020-02-04 20:59 ` Jens Axboe
2020-02-04 22:41 ` Bijan Mottahedeh
2020-02-24 23:32 ` Bijan Mottahedeh
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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