From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50673)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1Wrknb-0006Qa-Da
	for qemu-devel@nongnu.org; Tue, 03 Jun 2014 05:14:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1WrknU-0003fc-DA
	for qemu-devel@nongnu.org; Tue, 03 Jun 2014 05:14:27 -0400
Date: Tue, 3 Jun 2014 11:14:16 +0200
From: Stefan Hajnoczi <stefanha@gmail.com>
Message-ID: <20140603091416.GD19366@stefanha-thinkpad.muc.redhat.com>
References: <53863BC6.3040108@profihost.ag> <53863C9A.4040905@profihost.ag>
	<606EBA1F-638A-487D-8551-8D183D79937E@profihost.ag>
	<20140602134007.GG3049@stefanha-thinkpad.redhat.com>
	<538CD167.1080100@profihost.ag>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <538CD167.1080100@profihost.ag>
Subject: Re: [Qemu-devel] qemu 2.0 segfaults in event notifier
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: "famz@redhat.com" <famz@redhat.com>, qemu-devel <qemu-devel@nongnu.org>, "qemu-stable@nongnu.org" <qemu-stable@nongnu.org>

On Mon, Jun 02, 2014 at 09:32:55PM +0200, Stefan Priebe wrote:
> Am 02.06.2014 15:40, schrieb Stefan Hajnoczi:
> >On Fri, May 30, 2014 at 04:10:39PM +0200, Stefan Priebe wrote:
> new trace:
> (gdb) bt
> #0  0x00007f69e421c43f in event_notifier_set (e=0x124) at
> util/event_notifier-posix.c:97
> #1  0x00007f69e3e37afc in aio_notify (ctx=0x0) at async.c:246
> #2  0x00007f69e3e37697 in qemu_bh_schedule (bh=0x7f5dac217f60) at
> async.c:128
> #3  0x00007f69e3e8bc44 in rbd_finish_aiocb (c=0x7f5dac0c3f30,
> rcb=0x7f5dafa50610) at block/rbd.c:585
> #4  0x00007f69e17bee44 in librbd::AioCompletion::complete() () from
> /usr/lib/librbd.so.1
> #5  0x00007f69e17be832 in
> librbd::AioCompletion::complete_request(CephContext*, long) () from
> /usr/lib/librbd.so.1
> #6  0x00007f69e1c946ba in Context::complete(int) () from
> /usr/lib/librados.so.2
> #7  0x00007f69e17f1e85 in ObjectCacher::C_WaitForWrite::finish(int) () from
> /usr/lib/librbd.so.1
> #8  0x00007f69e1c946ba in Context::complete(int) () from
> /usr/lib/librados.so.2
> #9  0x00007f69e1d373c8 in Finisher::finisher_thread_entry() () from
> /usr/lib/librados.so.2
> #10 0x00007f69dbd43b50 in start_thread () from
> /lib/x86_64-linux-gnu/libpthread.so.0
> #11 0x00007f69dba8e13d in clone () from /lib/x86_64-linux-gnu/libc.so.6
> #12 0x0000000000000000 in ?? ()
> 
> this i another core dump so address differ:
> (gdb) p *(QEMUBH*)0x7f5dac217f60
> $1 = {ctx = 0x0, cb = 0x7f69e3e8bb75 <rbd_finish_bh>, opaque =
> 0x7f5dafa50610, next = 0x7f69e6b04d10, scheduled = false,
>   idle = false, deleted = true}

Thanks, this releaved the bug.

I will CC you on a fix.  Please try it out and reply with "Tested-by:
Stefan Priebe <s.priebe@profihost.ag>" if it works.

Stefan