From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fabian Ebner <f.ebner@proxmox.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
"open list:Linux io_uring" <qemu-block@nongnu.org>,
Stefan Hajnoczi <stefanha@gmail.com>,
Julia Suvorova <jusual@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
Aarushi Mehta <mehta.aaru20@gmail.com>,
Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: [PATCH v2] block/io_uring: resubmit when result is -EAGAIN
Date: Thu, 29 Jul 2021 17:15:53 +0100 [thread overview]
Message-ID: <YQLUOVXgDjRuAZLQ@stefanha-x1.localdomain> (raw)
In-Reply-To: <20210729091029.65369-1-f.ebner@proxmox.com>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
On Thu, Jul 29, 2021 at 11:10:29AM +0200, Fabian Ebner wrote:
> Linux SCSI can throw spurious -EAGAIN in some corner cases in its
> completion path, which will end up being the result in the completed
> io_uring request.
>
> Resubmitting such requests should allow block jobs to complete, even
> if such spurious errors are encountered.
>
> Co-authored-by: Stefan Hajnoczi <stefanha@gmail.com>
> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
> ---
>
> Changes from v1:
> * Focus on what's relevant for the patch itself in the commit
> message.
> * Add Stefan's comment.
> * Add Stefano's R-b tag (I hope that's fine, since there was no
> change code-wise).
>
> block/io_uring.c | 16 +++++++++++++++-
> 1 file changed, 15 insertions(+), 1 deletion(-)
Thanks, applied to my block tree:
https://gitlab.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-07-29 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 9:10 [PATCH v2] block/io_uring: resubmit when result is -EAGAIN Fabian Ebner
2021-07-29 9:54 ` Stefano Garzarella
2021-07-29 16:15 ` Stefan Hajnoczi [this message]
2021-08-02 12:40 ` Kevin Wolf
2021-08-04 14:50 ` Stefano Garzarella
2021-08-04 16:52 ` Kevin Wolf
2021-08-05 8:31 ` Stefano Garzarella
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=YQLUOVXgDjRuAZLQ@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=f.ebner@proxmox.com \
--cc=jusual@redhat.com \
--cc=kwolf@redhat.com \
--cc=mehta.aaru20@gmail.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@gmail.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).