qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Halsey Pian" <halsey.pian@gmail.com>
To: qemu-devel@nongnu.org
Cc: halsey.pian@gmail.com
Subject: [Qemu-devel] [Bug] qemu_coroutine_enter abort and report error "Co-routine re-entered recursively"
Date: Fri, 6 Mar 2015 15:03:58 +0800	[thread overview]
Message-ID: <009a01d057db$baf86640$30e932c0$@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2074 bytes --]

Hi All,

 

I have two threads to write two seperate qcow2 files,  but after a while,  the writing would be aborted in qemu_coroutine_enter, and report error “"Co-routine re-entered recursively” .

 

Qemu should be thread safe, right? It seems that there are some variables is not thread safe? Could you have a chance to look it? Thanks!

 

Call stack:

 

#0 0x7ffff5e18989            __GI_raise(sig=sig@entry=6) (../nptl/sysdeps/unix/sysv/linux/raise.c:56)

#1 0x7ffff5e1a098            __GI_abort() (abort.c:90)

#2 0x7ffff728c034            qemu_coroutine_enter(co=0x7fffe0004800, opaque=0x0) (qemu-coroutine.c:117)

#3 0x7ffff727df39            bdrv_co_io_em_complete(opaque=0x7ffff7fd6ae0, ret=0) (block.c:4847)

#4 0x7ffff7270314            thread_pool_completion_bh(opaque=0x7fffe0006ad0) (thread-pool.c:187)

#5 0x7ffff726f873             aio_bh_poll(ctx=0x7fffe0001d00) (async.c:82)

#6 0x7ffff728340b            aio_dispatch(ctx=0x7fffe0001d00) (aio-posix.c:137)

#7 0x7ffff72837b0            aio_poll(ctx=0x7fffe0001d00, blocking=true) (aio-posix.c:248)

#8 ??     0x00007ffff72795a8 in bdrv_prwv_co (bs=0x7fffdc0021c0, offset=12071639552, qiov=0x7fffe67fa590, is_write=true, flags=(unknown: 0)) (block.c:2703)

#9 ??     0x00007ffff727966a in bdrv_rw_co (bs=0x7fffdc0021c0, sector_num=23577421, buf=0x7fffe4629250 "\234\b\335Ǽ\254\213q\301\366\315=\005oI\301\245=\373\004+2?H\212\025\035+\262\274C;X\301FaP\324\335\061ҝ&Y\316=\347\335\020\365\003goɿ\214\312S=\v2]\373\363C\311\341\334\r5k\346k\204\332\023\264\315陌\230\203J\222u\214\066", nb_sectors=128, is_write=true, flags=(unknown: 0)) (block.c:2726)

#10 0x7ffff7279758          bdrv_write(bs=0x7fffdc0021c0, sector_num=23577421, buf=0x7fffe4629250 "\234\b\335Ǽ\254\213q\301\366\315=\005oI\301\245=\373\004+2?H\212\025\035+\262\274C;X\301FaP\324\335\061ҝ&Y\316=\347\335\020\365\003goɿ\214\312S=\v2]\373\363C\311\341\334\r5k\346k\204\332\023\264\315陌\230\203J\222u\214\066", nb_sectors=128) (block.c:2760)

 

 

Best Regards

Halsey Pian

 


[-- Attachment #2: Type: text/html, Size: 6000 bytes --]

             reply	other threads:[~2015-03-06  7:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06  7:03 Halsey Pian [this message]
2015-03-06  7:15 ` [Qemu-devel] [Bug] qemu_coroutine_enter abort and report error "Co-routine re-entered recursively" Halsey Pian
2015-03-06  9:44 ` Paolo Bonzini
2015-03-06 11:10   ` Halsey Pian

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='009a01d057db$baf86640$30e932c0$@gmail.com' \
    --to=halsey.pian@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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).