From: Max Reitz <mreitz@redhat.com>
To: John Snow <jsnow@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] sigsegv in chardev on iotest 045 (raw)
Date: Wed, 5 Jun 2019 18:22:41 +0200 [thread overview]
Message-ID: <aeafd8bd-4027-eb21-fe68-f76f656e514a@redhat.com> (raw)
In-Reply-To: <e7401f4d-e69b-2930-b070-fb0da55e4b98@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
On 05.06.19 03:15, John Snow wrote:
> Running tests on a development branch (I haven't touched chardev stuff,
> I swear!); I ran into the below crash where s->ioc was NULL. I don't
> have the time to investigate at this exact moment, so please excuse the
> hasty report so I don't forget to tell someone.
>
> It does not reproduce consistently, and I can't get it to show up again.
>
> (Is this maybe just a race on close where the device went away too fast
> and it had nowhere to print the information? --js)
Your back trace looks exactly like what I posted in
http://lists.nongnu.org/archive/html/qemu-devel/2018-12/msg05579.html .
No, I don’t think anybody has posted a fix for this so far. I know
other people saw similar issues.
I know what I have on my test branch (which contains various fixes to
make all iotests run or at least pass those which are terminally broken):
https://git.xanclic.moe/XanClic/qemu/commit/c52433f218c61ef608ab4d9abb56e1f705a3ae22
I have a lot of patches on my test branch. (15, to be exact.)
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-05 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 1:15 [Qemu-devel] sigsegv in chardev on iotest 045 (raw) John Snow
2019-06-05 16:22 ` Max Reitz [this message]
2019-06-05 17:21 ` John Snow
2019-06-05 19:34 ` Max Reitz
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=aeafd8bd-4027-eb21-fe68-f76f656e514a@redhat.com \
--to=mreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kraxel@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).