From: Amit Shah <amit.shah@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: mdroth@linux.vnet.ibm.com, qemu-devel <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] virtio-serial: Fix segfault on guest boot
Date: Fri, 17 Jun 2011 14:14:27 +0530 [thread overview]
Message-ID: <20110617084427.GC18513@amit-x200.redhat.com> (raw)
In-Reply-To: <m3hb7o3nn0.fsf@blackfin.pond.sub.org>
On (Fri) 17 Jun 2011 [09:47:31], Markus Armbruster wrote:
> Amit Shah <amit.shah@redhat.com> writes:
>
> > On (Thu) 16 Jun 2011 [13:38:49], Luiz Capitulino wrote:
> >> If I start qemu with:
> >>
> >> # qemu -hda disks/test.img -enable-kvm -m 1G -snapshot \
> >> -device virtio-serial \
> >> -chardev socket,host=localhost,port=1234,server,nowait,id=foo \
> >> -device virtserialport,chardev=foo,name=org.qemu.guest_agent
> >>
> >> I get a segfault when booting a Fedora 14 guest. The backtrace says:
> >>
> >> Program terminated with signal 11, Segmentation fault.
> >> #0 0x0000000000420850 in handle_control_message (vser=0x3732bd0, buf=0x2c173e0, len=8) at /home/lcapitulino/src/qmp-unstable/hw/virtio-serial-bus.c:335
> >> 335 info = DO_UPCAST(VirtIOSerialPortInfo, qdev, port->dev.info);
> >
> > Strange, I've not seen it so far in my testing (neither in the daily
> > test runs of the virtio-serial testsuite).
> >
> >> I've also bisected this and git points out to commit:
> >>
> >> commit a15bb0d6a981de749452a5180fc8084d625671da
> >> Author: Markus Armbruster <armbru@redhat.com>
> >> Date: Wed May 25 14:21:13 2011 +0200
> >>
> >> virtio-serial: Drop redundant VirtIOSerialPort member info
> >>
> >> I think what's happening is that the device is not initialized on a
> >> VIRTIO_CONSOLE_DEVICE_READY event.
>
> Really?
>
> I believe the device is initialized just fine, but the message refers to
> a nonexistant port. The check after find_port_by_id() suggests that's
> expected for VIRTIO_CONSOLE_DEVICE_READY.
What's happening is VIRTIO_CONSOLE_DEVICE_READY is a message for the
whole device, not for an individual port. So port is NULL. All other
messages (currently) are port-specific, so they have 'port' set to
something. The commit message needs to be tweaked for this.
>
> >> Moving the DO_UPCAST() call to
> >> the other events fixes the problem to me.
> >>
> >> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> >> ---
> >> hw/virtio-serial-bus.c | 4 ++--
> >> 1 files changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/hw/virtio-serial-bus.c b/hw/virtio-serial-bus.c
> >> index 9a12104..579f676 100644
> >> --- a/hw/virtio-serial-bus.c
> >> +++ b/hw/virtio-serial-bus.c
> >> @@ -332,8 +332,6 @@ static void handle_control_message(VirtIOSerial *vser, void *buf, size_t len)
> >> if (!port && cpkt.event != VIRTIO_CONSOLE_DEVICE_READY)
> >> return;
> >>
> >> - info = DO_UPCAST(VirtIOSerialPortInfo, qdev, port->dev.info);
> >> -
> >
> > Ah - this missed the !port check. It should be possible to do this in
> > a 'if (port)' block instead of replicating in the individual case
> > statements.
>
> You might have to do something like info = port ? DO_UPCAST(...) : NULL
> to avoid warnings about info used uninitialized.
That won't happen -- in the case where port is NULL, we shouldn't try
to use info. If we do get such a warning, it means there's a bug :-)
Amit
next prev parent reply other threads:[~2011-06-17 8:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 16:38 [Qemu-devel] [PATCH] virtio-serial: Fix segfault on guest boot Luiz Capitulino
2011-06-17 6:47 ` Amit Shah
2011-06-17 7:47 ` Markus Armbruster
2011-06-17 8:44 ` Amit Shah [this message]
2011-06-17 13:16 ` Luiz Capitulino
2011-06-17 13:21 ` Luiz Capitulino
2011-06-17 16:09 ` Amit Shah
2011-06-17 18:08 ` Luiz Capitulino
2011-06-18 3:42 ` Amit Shah
2011-06-18 21:43 ` Blue Swirl
2011-06-22 4:53 ` Amit Shah
2011-06-26 17:43 ` Blue Swirl
2011-06-27 9:48 ` [Qemu-devel] 80-column rule and breaking output statements Amit Shah
2011-07-01 19:43 ` Blue Swirl
2011-07-02 8:38 ` Stefan Hajnoczi
2011-07-04 6:05 ` Amit Shah
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=20110617084427.GC18513@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.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).