From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] tpm-tis-test and tpm-crb-test crash on OSX
Date: Fri, 16 Mar 2018 14:18:30 +0000 [thread overview]
Message-ID: <20180316141830.GL3066@redhat.com> (raw)
In-Reply-To: <e971a441-2118-e07a-ee77-56758ccf41af@linux.vnet.ibm.com>
On Fri, Mar 16, 2018 at 09:45:59AM -0400, Stefan Berger wrote:
> On 03/16/2018 09:41 AM, Marc-André Lureau wrote:
> > Hi
> >
> > On Fri, Mar 16, 2018 at 2:37 PM, Marc-André Lureau
> > <marcandre.lureau@gmail.com> wrote:
> > > Hi
> > >
> > > On Fri, Mar 16, 2018 at 2:27 PM, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > > > At least the tpm_emu_tpm_thread() there is only something in the test
> > > > suite, so the real system emulator code isn't at risk of crashing.
> > > >
> > > > Feels like the thread simply should *not* use error_abort, and instead
> > > > have a more graceful way to exit when the socket closes
> > > >
> > > The code expects the read() to return 0 on disconnect, not an error.
> > > Apparently this works on !osx. Should we adapt qio-channel-socket to
> > > return 0 in this case on osx too?
> > Oh I see, it calls close() on the same end, that's not correct. I
> > wonder if shutdown would be better. Other suggestions?
> >
> We could send the thread a special message, like 0xff ff ff ff, and that
> terminates it...
If there's no resource cleanup in this test suite thread to worry about
could just pthread_cancel() it
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-03-16 14:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 13:12 [Qemu-devel] tpm-tis-test and tpm-crb-test crash on OSX Peter Maydell
2018-03-16 13:24 ` Peter Maydell
2018-03-16 13:27 ` Daniel P. Berrangé
2018-03-16 13:37 ` Marc-André Lureau
2018-03-16 13:41 ` Marc-André Lureau
2018-03-16 13:45 ` Stefan Berger
2018-03-16 14:08 ` Stefan Berger
2018-03-16 14:09 ` Marc-André Lureau
2018-03-16 14:35 ` Stefan Berger
2018-03-16 14:18 ` Daniel P. Berrangé [this message]
2018-03-16 13:43 ` Daniel P. Berrangé
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=20180316141830.GL3066@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@gmail.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 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).