From owner-freebsd-fs@FreeBSD.ORG  Fri Apr 16 20:10:03 2010
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id DADD91065675
	for <freebsd-fs@hub.freebsd.org>; Fri, 16 Apr 2010 20:10:03 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id B82758FC17
	for <freebsd-fs@hub.freebsd.org>; Fri, 16 Apr 2010 20:10:03 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o3GKA3Q7082759
	for <freebsd-fs@freefall.freebsd.org>; Fri, 16 Apr 2010 20:10:03 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o3GKA3gH082758;
	Fri, 16 Apr 2010 20:10:03 GMT (envelope-from gnats)
Date: Fri, 16 Apr 2010 20:10:03 GMT
Message-Id: <201004162010.o3GKA3gH082758@freefall.freebsd.org>
To: freebsd-fs@FreeBSD.org
From: Andriy Gapon <avg@icyb.net.ua>
Cc: 
Subject: Re: kern/145339: [zfs] deadlock after detaching block device from
 raidz pool
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Andriy Gapon <avg@icyb.net.ua>
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Apr 2010 20:10:03 -0000

The following reply was made to PR kern/145339; it has been noted by GNATS.

From: Andriy Gapon <avg@icyb.net.ua>
To: bug-followup@FreeBSD.org, Alex.Bakhtin@gmail.com
Cc: Pawel Jakub Dawidek <pjd@FreeBSD.org>
Subject: Re: kern/145339: [zfs] deadlock after detaching block device from
 raidz pool
Date: Fri, 16 Apr 2010 23:09:38 +0300

 Are you sure that this is a deadlock?
 If yes, could you please describe what you see in more details.
 
 I am asking because to me it seems like a NULL pointer crash:
 > Fatal trap 12: page fault while in kernel mode
 > cpuid = 1; apic id = 01
 > fault virtual address = 0x48
 
 It looks like perhaps zio->io_vd became NULL while an I/O response was traveling
 up and vdev_geom_io_intr was not prepared to handle that.
 
 > _mtx_lock_flags() at _mtx_lock_flags+0x39
 > vdev_geom_io_intr() at vdev_geom_io_intr+0x62
 > g_io_schedule_up() at g_io_schedule_up+0xed
 > g_up_procbody() at g_up_procbody+0x6f
 > fork_exit() at fork_exit+0x12a
 > fork_trampoline() at fork_trampoline+0xe
 
 
 -- 
 Andriy Gapon