From owner-freebsd-current@FreeBSD.ORG Mon Sep 8 21:31:01 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5DF2B1065680; Mon, 8 Sep 2008 21:31:01 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id D72A28FC1A; Mon, 8 Sep 2008 21:31:00 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [IPv6:2001:470:1f11:75:2a0:d2ff:fe18:8b38]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m88LUZtT096483; Mon, 8 Sep 2008 17:30:54 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 8 Sep 2008 17:26:51 -0400 User-Agent: KMail/1.9.7 References: <48BF911F.4000600@freebsd.org> In-Reply-To: <48BF911F.4000600@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809081726.51942.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:2001:470:1f11:75::1]); Mon, 08 Sep 2008 17:30:55 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/8162/Thu Sep 4 12:38:45 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: David Xu Subject: Re: lockmgr_args, lock order reversal: (sleepable after non-sleepable) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2008 21:31:01 -0000 On Thursday 04 September 2008 03:41:19 am David Xu wrote: > I saw so many LORs like following, I think this is a false reporting > because the interlock is released by lockmgr whether the thread is > blocked or not, shouldn't WITNESS_CHECKORDER bypass this interlock ? I have a patch to fix this, I will commit it soon. > lock order reversal: (sleepable after non-sleepable) > 1st 0xc48d728c vnode interlock (vnode interlock) @ > fs/devfs/devfs_vnops.c:286 > 2nd 0xc48d7270 devfs (devfs) @ kern/vfs_subr.c:2051 > KDB: stack backtrace: > db_trace_self_wrapper(c0b6d1e1,c4199a2c,c07f1d35,4,c0b68bf7,...) at > db_trace_self_wrapper+0x26 > kdb_backtrace(4,c0b68bf7,c0de8a58,c44768d0,c4199b64,...) at > kdb_backtrace+0x29 > _witness_debugger(c0b6fa7b,c48d6000,c0b761c4,c44768d0,c0b7679d,...) at > _witness_debugger+0x25 > witness_checkorder(c48d6000,1,c0b76794,174,c0b68bf7,...) at > witness_checkorder+0x7c9 > __lockmgr_args(c48d6000,200100,c48d601c,0,0,...) at __lockmgr_args+0x230 > vfs_busy(c48d6000,200,0,1,c44c6d20,...) at vfs_busy+0x1bc > vfs_mount_alloc(0,c0c3bae0,c0b7653a,c44b1400,c0831580,...) at > vfs_mount_alloc+0x74 > vfs_mountroot(c0caef30,4,c0b64bc9,264,0,...) at vfs_mountroot+0x272 > start_init(0,c4199d38,c0b66578,322,c44c4d0c,...) at start_init+0x65 > fork_exit(c077a040,0,c4199d38) at fork_exit+0xb8 > > > David Xu > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- John Baldwin