qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Greg Kurz <gkurz@linux.vnet.ibm.com>
Subject: [Qemu-devel] 9pfs is broken in 2.5 (SIGSEGV) (bisected)
Date: Sat, 19 Dec 2015 11:05:16 +0300	[thread overview]
Message-ID: <56750FBC.6020106@msgid.tls.msk.ru> (raw)

When trying to mount a 9p filesystem in guest in 2.5 qemu,
qemu immediately segfaults.

 qemu-system-x86_64 ...
  -fsdev local,security_model=none,id=fsd0,path=/tmp
  -device virtio-9p-pci,fsdev=fsd0,mount_tag=fsd0


 mount -t 9p -o trans=virtio,version=9p2000.u fsd0 /mnt
 (SIGSEGV)

The problem goes down to the following commit:

commit ebac1202c95a4f1b76b6ef3f0f63926fa76e753e
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Fri Nov 27 12:43:06 2015 +0100

    virtio-9p: use QEMU thread pool

    The QEMU thread pool already has a mechanism to invoke callbacks in the main
    thread.  It does not need an EventNotifier and it is more efficient too.
    Use it instead of GAsyncQueue + GThreadPool + glue.

    As a side effect, it silences Coverity's complaint about an unchecked
    return value for event_notifier_init.

    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
    Reviewed-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
    (removed no more needed #include <glib.h> from virtio-9p-coth.h)
    Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>

This is a heads-up for now, digging further.

/mjt

             reply	other threads:[~2015-12-19  8:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19  8:05 Michael Tokarev [this message]
2015-12-19  8:15 ` [Qemu-devel] 9pfs is broken in 2.5 (SIGSEGV) (bisected) Michael Tokarev
     [not found] ` <5675120F.3000904@tls.msk.ru>
2015-12-19  9:16   ` Michael Tokarev
2015-12-19 18:41     ` Greg Kurz

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=56750FBC.6020106@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=gkurz@linux.vnet.ibm.com \
    --cc=pbonzini@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).