From: Jan Kiszka <jan.kiszka@web.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] slirp-related crash
Date: Sun, 12 Feb 2012 21:24:04 +0100 [thread overview]
Message-ID: <4F381FE4.3050009@web.de> (raw)
In-Reply-To: <20120212183407.GA4534@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1991 bytes --]
On 2012-02-12 19:34, Michael S. Tsirkin wrote:
> It seems somewhat easy to crash qemu with slirp if we queue multiple packets.
> I didn't investigate further yet so I don't know if this
> is a regression. Anyone knowledgeable about slirp wants to take a look?
>
> /home/mst/qemu-test/bin/qemu-system-x86_64 -enable-kvm -m 1G -drive
> file=/home/mst/rhel6.qcow2 -netdev user,id=bar -net
> nic,netdev=bar,model=e1000,macaddr=52:54:00:12:34:57 -redir
> tcp:8022::22 -vnc :1 -monitor stdio
>
> While guest is booting, quickly do this
>
> ssh localhost -p 8022
> CTRL-C
> ssh localhost -p 8022
> CTRL-C
> ssh localhost -p 8022
> CTRL-C
> ssh localhost -p 8022
> CTRL-C
Confirmed. A single canceled connection prior the interface setup is
enough. Possibly something is not properly removed / cleaned up here.
Will see if I find some time to debug, can't promise.
Jan
>
> When guest triest to bring up link,
> qemu crashes:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff7e4f8a7 in slirp_insque (a=0x0, b=0x7ffff91681f0) at
> slirp/misc.c:27
> 27 element->qh_link = head->qh_link;
> (gdb) where
> #0 0x00007ffff7e4f8a7 in slirp_insque (a=0x0, b=0x7ffff91681f0) at
> slirp/misc.c:27
> #1 0x00007ffff7e4ddd8 in if_start (slirp=0x7ffff8b0e4f0) at
> slirp/if.c:194
> #2 0x00007ffff7e51290 in slirp_select_poll (readfds=0x7fffffffdfe0,
> writefds=
> 0x7fffffffdf60, xfds=0x7fffffffdee0, select_error=0) at
> slirp/slirp.c:588
> #3 0x00007ffff7e114c3 in main_loop_wait (nonblocking=<value optimized
> out>)
> at main-loop.c:466
> #4 0x00007ffff7e09ed4 in main_loop (argc=<value optimized out>,
> argv=<value optimized out>, envp=<value optimized out>)
> at /home/mst/scm/qemu/vl.c:1482
> #5 main (argc=<value optimized out>, argv=<value optimized out>,
> envp=<value optimized out>) at /home/mst/scm/qemu/vl.c:3525
> (gdb) p element
> $1 = (struct quehead *) 0x0
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-02-12 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-12 18:34 [Qemu-devel] slirp-related crash Michael S. Tsirkin
2012-02-12 20:24 ` Jan Kiszka [this message]
2012-02-13 15:27 ` Zhi Yong Wu
2012-02-13 19:35 ` Jan Kiszka
2012-02-13 19:38 ` Jan Kiszka
2012-02-13 20:43 ` Alex Bradbury
2012-02-13 21:01 ` Jan Kiszka
2012-02-14 8:22 ` Stefan Hajnoczi
2012-02-14 10:14 ` Jan Kiszka
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=4F381FE4.3050009@web.de \
--to=jan.kiszka@web.de \
--cc=mst@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 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.