From owner-freebsd-ia64@FreeBSD.ORG Sun Jul 12 14:54:18 2009 Return-Path: Delivered-To: freebsd-ia64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27AC8106564A for ; Sun, 12 Jul 2009 14:54:18 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirj.bris.ac.uk (dirj.bris.ac.uk [137.222.10.78]) by mx1.freebsd.org (Postfix) with ESMTP id DBA758FC08 for ; Sun, 12 Jul 2009 14:54:17 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from isis.bris.ac.uk ([137.222.10.63]) by dirj.bris.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1MQ0RN-0003Ho-R0; Sun, 12 Jul 2009 15:54:17 +0100 Received: from mech-cluster238.men.bris.ac.uk ([137.222.187.238]) by isis.bris.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1MQ0RM-0003vJ-US; Sun, 12 Jul 2009 15:54:09 +0100 Received: from mech-cluster238.men.bris.ac.uk (localhost.men.bris.ac.uk [127.0.0.1]) by mech-cluster238.men.bris.ac.uk (8.14.3/8.14.3) with ESMTP id n6CEs8FP023643; Sun, 12 Jul 2009 15:54:08 +0100 (BST) (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster238.men.bris.ac.uk (8.14.3/8.14.3/Submit) id n6CEs5vf023642; Sun, 12 Jul 2009 15:54:05 +0100 (BST) (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster238.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Sun, 12 Jul 2009 15:54:05 +0100 From: Anton Shterenlikht To: bzeeb+freebsd+lor@zabbadoz.net Message-ID: <20090712145405.GA23614@mech-cluster238.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -1.4 X-Spam-Level: - Cc: freebsd-ia64@freebsd.org Subject: LOR #261 X-BeenThere: freebsd-ia64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the IA-64 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jul 2009 14:54:18 -0000 FreeBSD 8.0-BETA1 ia64 LOR below looks like LOR #261, but the line numbers are different. What does state "cannot deadlock" mean in your table? many thanks anton ************************* lock order reversal: 1st 0xa00000001e5adcf0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2558 2nd 0xe000000010866a00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:285 KDB: stack backtrace: db_trace_self(0xe000000004135d60) at db_trace_self+0x20 db_trace_self_wrapper(0xe00000000443add0) at db_trace_self_wrapper+0x70 kdb_backtrace(0xe0000000049da960, 0xe0000000044639d0) at kdb_backtrace+0xc0 _witness_debugger(0x1, 0xe000000004888610, 0xe000000004465270, 0x999, 0xe0000000048ac640) at _witness_debugger+0x60 witness_checkorder(0xe000000010866a00, 0x9, 0xffffffffffffffff, 0x11d, 0x0) at witness_checkorder+0x12c0 _sx_xlock(0xe000000010866a00, 0x0, 0xe0000000048ac640, 0x11d) at _sx_xlock+0xc0 ufsdirhash_acquire(0xe000000010a9a348, 0xe000000010866a00, 0xe00000000477eaf0, 0x38b) at ufsdirhash_acquire+0x50 ufsdirhash_remove(0xe000000010a9a348, 0xa00000001f760018, 0x18, 0xa000000032b45308) at ufsdirhash_remove+0x20 ufs_dirremove(0xe000000010b46760, 0xe000000010a39d88, 0x0, 0x0) at ufs_dirremove+0x240 ufs_remove(0xa000000032b453d8, 0xe000000010a39d88, 0xe0000000045096f0) at ufs_remove+0xe0 VOP_REMOVE_APV(0xe0000000049acdd0, 0xa000000032b453d8, 0xe000000010b459d0, 0xe000000004509760) at VOP_REMOVE_APV+0x1c0 kern_unlinkat(0xe000000010850b10, 0xffffffffffffff9c, 0x200000004041b048, 0x0) at kern_unlinkat+0x2f0 kern_unlink(0xe000000010850b10, 0x200000004041b048, 0x0) at kern_unlink+0x30 unlink(0xe000000010850b10, 0xa000000032b454e8, 0xe0000000048283e0, 0x58f) at unlink+0x30 syscall(0xa000000032b45400, 0xa, 0x200000004041af40, 0xe000000010850b10, 0xe000000010848cd8, 0xe000000004982690, 0xa, 0xa000000032b454e8) at syscall+0x3e0 epc_syscall_return() at epc_syscall_return -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423