From: Dario Faggioli <dfaggioli@suse.com>
To: "faithilikerun@gmail.com" <faithilikerun@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "stefanha@redhat.com" <stefanha@redhat.com>,
"hreitz@redhat.com" <hreitz@redhat.com>,
"kwolf@redhat.com" <kwolf@redhat.com>,
"sgarzare@redhat.com" <sgarzare@redhat.com>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
"jusual@redhat.com" <jusual@redhat.com>,
"mehta.aaru20@gmail.com" <mehta.aaru20@gmail.com>
Subject: Re: [PATCH] block/io_uring: revert "Use io_uring_register_ring_fd() to skip fd operations"
Date: Fri, 7 Oct 2022 15:38:05 +0000 [thread overview]
Message-ID: <5ead5696ff9b4cd7ce89190d368d53a7e16c30a3.camel@suse.com> (raw)
In-Reply-To: <20220924144815.5591-1-faithilikerun@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
Yes, we did hit this bug as well, in the QEMU 7.1 package, for openSUSE
Tumbleweed (more info
here: https://bugzilla.suse.com/show_bug.cgi?id=1204082)
FWIW, I can confirm that applying this patch fixes the issue, so this
can have:
On Sat, 2022-09-24 at 22:48 +0800, Sam Li wrote:
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1193
>
> [...]
>
> This reverts commit e2848bc574fe2715c694bf8fe9a1ba7f78a1125a
> and 77e3f038af1764983087e3551a0fde9951952c4d.
>
> Signed-off-by: Sam Li <faithilikerun@gmail.com>
>
Tested-by: Dario Faggioli <dfaggioli@suse.com>
Regards
--
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-10-07 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 14:48 [PATCH] block/io_uring: revert "Use io_uring_register_ring_fd() to skip fd operations" Sam Li
2022-10-07 15:38 ` Dario Faggioli [this message]
2022-10-10 8:47 ` Stefano Garzarella
2022-10-21 9:48 ` Kevin Wolf
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=5ead5696ff9b4cd7ce89190d368d53a7e16c30a3.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=faithilikerun@gmail.com \
--cc=hreitz@redhat.com \
--cc=jusual@redhat.com \
--cc=kwolf@redhat.com \
--cc=mehta.aaru20@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.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).