qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] [vhost-user BUG ?] QEMU process segfault when shutdown or reboot with vhost-user
@ 2015-11-03 13:01 zhanghailiang
  2015-11-03 14:54 ` Marc-André Lureau
  0 siblings, 1 reply; 5+ messages in thread
From: zhanghailiang @ 2015-11-03 13:01 UTC (permalink / raw)
  To: qemu-devel@nongnu.org; +Cc: jasowang, peter.huangpeng, stefanha@redhat.com, mst

Hi,

We catch a segfault in our project.

Qemu version is 2.3.0

The Stack backtrace is:
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00007f7ad9280b2f in qemu_deliver_packet (sender=<optimized out>, flags=<optimized out>, data=<optimized out>, size=100, opaque=
     0x7f7ad9d6db10) at net/net.c:510
#2  0x00007f7ad92831fa in qemu_net_queue_deliver (size=<optimized out>, data=<optimized out>, flags=<optimized out>,
     sender=<optimized out>, queue=<optimized out>) at net/queue.c:157
#3  qemu_net_queue_flush (queue=0x7f7ad9d39630) at net/queue.c:254
#4  0x00007f7ad9280dac in qemu_flush_or_purge_queued_packets (nc=0x7f7ad9d6db10, purge=true) at net/net.c:539
#5  0x00007f7ad9280e76 in net_vm_change_state_handler (opaque=<optimized out>, running=<optimized out>, state=100) at net/net.c:1214
#6  0x00007f7ad915612f in vm_state_notify (running=0, state=RUN_STATE_SHUTDOWN) at vl.c:1820
#7  0x00007f7ad906db1a in do_vm_stop (state=<optimized out>) at /usr/src/packages/BUILD/qemu-kvm-2.3.0/cpus.c:631
#8  vm_stop (state=RUN_STATE_SHUTDOWN) at /usr/src/packages/BUILD/qemu-kvm-2.3.0/cpus.c:1325
#9  0x00007f7ad915e4a2 in main_loop_should_exit () at vl.c:2080
#10 main_loop () at vl.c:2131
#11 main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at vl.c:4721
(gdb) p *(NetClientState *)0x7f7ad9d6db10
$1 = {info = 0x7f7ad9824520, link_down = 0, next = {tqe_next = 0x7f7ad0f06d10, tqe_prev = 0x7f7ad98b1cf0}, peer = 0x7f7ad0f06d10,
   incoming_queue = 0x7f7ad9d39630, model = 0x7f7ad9d39590 "vhost_user", name = 0x7f7ad9d39570 "hostnet0", info_str =
     "vhost-user to charnet0", '\000' <repeats 233 times>, receive_disabled = 0, destructor =
     0x7f7ad92821f0 <qemu_net_client_destructor>, queue_index = 0, rxfilter_notify_enabled = 0}
(gdb) p *(NetClientInfo *)0x7f7ad9824520
$2 = {type = NET_CLIENT_OPTIONS_KIND_VHOST_USER, size = 360, receive = 0, receive_raw = 0, receive_iov = 0, can_receive = 0, cleanup =
     0x7f7ad9288850 <vhost_user_cleanup>, link_status_changed = 0, query_rx_filter = 0, poll = 0, has_ufo =
     0x7f7ad92886d0 <vhost_user_has_ufo>, has_vnet_hdr = 0x7f7ad9288670 <vhost_user_has_vnet_hdr>, has_vnet_hdr_len = 0,
   using_vnet_hdr = 0, set_offload = 0, set_vnet_hdr_len = 0}
(gdb)

The corresponding codes where gdb reports error are: (We have added some codes in net.c)
ssize_t qemu_deliver_packet(NetClientState *sender,
                             unsigned flags,
                             const uint8_t *data,
                             size_t size,
                             void *opaque)
{
     NetClientState *nc = opaque;
     ssize_t ret;

     if (nc->link_down) {
         return size;
     }

     if (nc->receive_disabled) {
         return 0;
     }

     if (flags & QEMU_NET_PACKET_FLAG_RAW && nc->info->receive_raw) {
         ret = nc->info->receive_raw(nc, data, size);
     } else {
         ret = nc->info->receive(nc, data, size);   ----> Here is 510 line
     }

I'm not quite familiar with vhost-user, but for vhost-user, these two callback functions seem to be always NULL,
Why we can come here ?
Is it an error to add VM state change handler for vhost-user ?

Thanks,
zhanghailiang

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2015-11-04  8:13 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-03 13:01 [Qemu-devel] [vhost-user BUG ?] QEMU process segfault when shutdown or reboot with vhost-user zhanghailiang
2015-11-03 14:54 ` Marc-André Lureau
2015-11-04  2:24   ` zhanghailiang
2015-11-04  3:19     ` Jason Wang
2015-11-04  8:12       ` zhanghailiang

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).