qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1729623 <1729623@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [Bug 1729623] [NEW] test-aio-multithread fails with 'Co-routine re-entered recursively'
Date: Fri, 3 Nov 2017 09:48:43 +0000	[thread overview]
Message-ID: <20171103094843.GC5078@stefanha-x1.localdomain> (raw)
In-Reply-To: <150963549061.4171.11895725981979057755.malonedeb@gac.canonical.com>

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

On Thu, Nov 02, 2017 at 03:11:30PM -0000, R.Nageswara Sastry wrote:
> Public bug reported:
> 
> git head is at fa73e146250181852c0915aa65df8d54d35485fa
> 
> configure with the following
> 
> ./configure --enable-attr --enable-bsd-user --enable-cap-ng\
>  --enable-coroutine-pool  --enable-crypto-afalg --enable-curl\
>  --enable-curses --enable-debug --enable-debug-info\
>  --enable-debug-tcg      --enable-fdt      --enable-gcrypt \
>  --enable-gnutls      --enable-gprof      --enable-gtk  \
>  --enable-guest-agent      --enable-kvm      --enable-libiscsi \
>  --enable-libssh2      --enable-linux-aio      --enable-linux-user \
>  --enable-live-block-migration      --enable-modules   \
>  --enable-numa      --enable-pie      --enable-profiler \
>  --enable-qom-cast-debug      --enable-rbd      --enable-replication  \
>  --enable-seccomp      --enable-smartcard      --enable-stack-protector \
>  --enable-system      --enable-tcg      --enable-tcg-interpreter  \
>  --enable-tools      --enable-tpm      --enable-trace-backend=ftrace \
>  --enable-user      --enable-vhost-net      --enable-vhost-scsi  \
>  --enable-vhost-user      --enable-vhost-vsock      --enable-virtfs  \ 
>  --enable-vnc      --enable-tpm      --enable-vnc-png   \
>  --enable-vnc-sasl      --enable-werror      --enable-xfsctl \
>  --enable-gcov --enable-debug-stack-usage
> 
> make -j 32
> 
> make test-aio-multithread V=1
> 
> ...
> File '/home/nasastry/qemu/include/qapi/qmp/qobject.h'
> No executable lines
> 
> MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} gtester -k --verbose -m=quick tests/test-aio-multithread
> TEST: tests/test-aio-multithread... (pid=86877)
>   /aio/multi/lifecycle:                                                OK
>   /aio/multi/schedule:                                                 Co-routine re-entered recursively
> FAIL

I cannot reproduce it locally.

Please run with gdb tests/test-aio-multithread and post the backtrace
when the "Co-routine re-entered recursively" message is printed using
the "thread apply all bt" gdb command.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  parent reply	other threads:[~2017-11-03  9:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 15:11 [Qemu-devel] [Bug 1729623] [NEW] test-aio-multithread fails with 'Co-routine re-entered recursively' R.Nageswara Sastry
2017-11-02 15:14 ` [Qemu-devel] [Bug 1729623] " R.Nageswara Sastry
2017-11-03  9:48 ` Stefan Hajnoczi [this message]
2017-11-06  4:57 ` R.Nageswara Sastry
2017-11-06 19:03   ` Stefan Hajnoczi
2018-01-03 17:15 ` Murilo Opsfelder Araújo

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=20171103094843.GC5078@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=1729623@bugs.launchpad.net \
    --cc=pbonzini@redhat.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).