From: Stefan Hajnoczi <stefanha@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com, quintela@redhat.com,
peterx@redhat.com, leobras@redhat.com, pbonzini@redhat.com,
qemu-block@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [PATCH 2/2] virtio: Drop out of coroutine context in virtio_load()
Date: Thu, 7 Sep 2023 14:40:31 -0400 [thread overview]
Message-ID: <20230907184031.GA1560640@fedora> (raw)
In-Reply-To: <20230905145002.46391-3-kwolf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3308 bytes --]
On Tue, Sep 05, 2023 at 04:50:02PM +0200, Kevin Wolf wrote:
> virtio_load() as a whole should run in coroutine context because it
> reads from the migration stream and we don't want this to block.
Is that "should" a "must" or a "can"?
If it's a "must" then virtio_load() needs assert(qemu_in_coroutine()).
But the previous patch mentioned that loadvm for snapshots calls it
outside coroutine context. So maybe it's a "can"?
>
> However, it calls virtio_set_features_nocheck() and devices don't
> expect their .set_features callback to run in a coroutine and therefore
> call functions that may not be called in coroutine context. To fix this,
> drop out of coroutine context for calling virtio_set_features_nocheck().
>
> Without this fix, the following crash was reported:
>
> #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
> #1 0x00007efc738c05d3 in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78
> #2 0x00007efc73873d26 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
> #3 0x00007efc738477f3 in __GI_abort () at abort.c:79
> #4 0x00007efc7384771b in __assert_fail_base (fmt=0x7efc739dbcb8 "", assertion=assertion@entry=0x560aebfbf5cf "!qemu_in_coroutine()",
> file=file@entry=0x560aebfcd2d4 "../block/graph-lock.c", line=line@entry=275, function=function@entry=0x560aebfcd34d "void bdrv_graph_rdlock_main_loop(void)") at assert.c:92
> #5 0x00007efc7386ccc6 in __assert_fail (assertion=0x560aebfbf5cf "!qemu_in_coroutine()", file=0x560aebfcd2d4 "../block/graph-lock.c", line=275,
> function=0x560aebfcd34d "void bdrv_graph_rdlock_main_loop(void)") at assert.c:101
> #6 0x0000560aebcd8dd6 in bdrv_register_buf ()
> #7 0x0000560aeb97ed97 in ram_block_added.llvm ()
> #8 0x0000560aebb8303f in ram_block_add.llvm ()
> #9 0x0000560aebb834fa in qemu_ram_alloc_internal.llvm ()
> #10 0x0000560aebb2ac98 in vfio_region_mmap ()
> #11 0x0000560aebb3ea0f in vfio_bars_register ()
> #12 0x0000560aebb3c628 in vfio_realize ()
> #13 0x0000560aeb90f0c2 in pci_qdev_realize ()
> #14 0x0000560aebc40305 in device_set_realized ()
> #15 0x0000560aebc48e07 in property_set_bool.llvm ()
> #16 0x0000560aebc46582 in object_property_set ()
> #17 0x0000560aebc4cd58 in object_property_set_qobject ()
> #18 0x0000560aebc46ba7 in object_property_set_bool ()
> #19 0x0000560aeb98b3ca in qdev_device_add_from_qdict ()
> #20 0x0000560aebb1fbaf in virtio_net_set_features ()
> #21 0x0000560aebb46b51 in virtio_set_features_nocheck ()
> #22 0x0000560aebb47107 in virtio_load ()
> #23 0x0000560aeb9ae7ce in vmstate_load_state ()
> #24 0x0000560aeb9d2ee9 in qemu_loadvm_state_main ()
> #25 0x0000560aeb9d45e1 in qemu_loadvm_state ()
> #26 0x0000560aeb9bc32c in process_incoming_migration_co.llvm ()
> #27 0x0000560aebeace56 in coroutine_trampoline.llvm ()
>
> Cc: qemu-stable@nongnu.org
> Buglink: https://issues.redhat.com/browse/RHEL-832
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> hw/virtio/virtio.c | 45 ++++++++++++++++++++++++++++++++++++++++-----
> 1 file changed, 40 insertions(+), 5 deletions(-)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-09-07 18:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 14:50 [PATCH 0/2] virtio: Drop out of coroutine context in virtio_load() Kevin Wolf
2023-09-05 14:50 ` [PATCH 1/2] vmstate: Mark VMStateInfo.get/put() coroutine_mixed_fn Kevin Wolf
2023-09-05 15:06 ` Peter Xu
2023-09-05 14:50 ` [PATCH 2/2] virtio: Drop out of coroutine context in virtio_load() Kevin Wolf
2023-09-07 18:40 ` Stefan Hajnoczi [this message]
2023-09-08 8:59 ` Kevin Wolf
2023-09-08 10:46 ` Stefan Hajnoczi
2023-10-17 5:19 ` Michael Tokarev
2023-10-17 8:48 ` Kevin Wolf
2023-10-17 13:06 ` Juan Quintela
2023-09-07 18:42 ` [PATCH 0/2] " Stefan Hajnoczi
2023-09-08 8:53 ` Kevin Wolf
2023-09-08 10:46 ` Stefan Hajnoczi
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=20230907184031.GA1560640@fedora \
--to=stefanha@redhat.com \
--cc=kwolf@redhat.com \
--cc=leobras@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=quintela@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).