From: Bart Van Assche <[email protected]>
To: Stefan Roesch <[email protected]>,
[email protected], [email protected], [email protected]
Cc: [email protected]
Subject: Re: [PATCH v1] block: blk_queue_enter() / __bio_queue_enter() must return -EAGAIN for nowait
Date: Mon, 12 Sep 2022 10:14:52 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 9/12/22 09:53, Stefan Roesch wrote:
> Today blk_queue_enter() and __bio_queue_enter() return -EBUSY for the
> nowait code path. This is not correct: they should return -EAGAIN
> instead.
Why is this considered incorrect? Please explain.
Since this patch also affects other code, e.g. NVMe pass-through, can
this patch break existing user space code by changing the value returned
to user space?
Thanks,
Bart.
next prev parent reply other threads:[~2022-09-12 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 16:53 [PATCH v1] block: blk_queue_enter() / __bio_queue_enter() must return -EAGAIN for nowait Stefan Roesch
2022-09-12 17:14 ` Bart Van Assche [this message]
2022-09-12 17:22 ` Jens Axboe
2022-09-13 21:08 ` Jens Axboe
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] \
[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