From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Stefan Berger" <stefanb@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] tpm_emu_test_wait_cond: code should not be reached
Date: Tue, 8 May 2018 15:03:27 +0100 [thread overview]
Message-ID: <20180508140327.GY5967@redhat.com> (raw)
In-Reply-To: <CAFEAcA_L3fy+MFh72=zX3pHtXP634Uhu0+G=nz-fMWaGC8muNw@mail.gmail.com>
On Tue, May 08, 2018 at 02:54:39PM +0100, Peter Maydell wrote:
> On 8 May 2018 at 14:48, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > This test has a couple of threads running, and passes &error_abort to
> > the qio_channel_socket_readv() function. So I expect that one thread
> > is closing the socket connection, and the other thread has not yet
> > shutdown cleanly, so tries to readv on a dead socket triggering the
> > error_abort. IOW, qio_channel_socket_readv is likely just the symptom
> > of brokeness somewhere else in the test, not the cause.
>
> That sounds familiar...didn't we have a thread about this a while back?
Yeah, I don't recall if it was related to this particular test, or
another similar situation in a different test.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-05-08 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 12:41 [Qemu-devel] tpm_emu_test_wait_cond: code should not be reached Philippe Mathieu-Daudé
2018-05-08 13:41 ` Peter Maydell
2018-05-08 13:48 ` Daniel P. Berrangé
2018-05-08 13:54 ` Peter Maydell
2018-05-08 14:03 ` Daniel P. Berrangé [this message]
2018-05-08 15:18 ` Stefan Berger
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=20180508140327.GY5967@redhat.com \
--to=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.