From owner-freebsd-bugs@freebsd.org Sat May 28 20:13:08 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04DE2B4E2B0 for ; Sat, 28 May 2016 20:13:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D1BE410E4 for ; Sat, 28 May 2016 20:13:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u4SKD7dl011043 for ; Sat, 28 May 2016 20:13:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 192923] Lock order reversal in vfs_bio.c bufwait Date: Sat, 28 May 2016 20:13:07 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mva@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2016 20:13:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192923 --- Comment #3 from Marcus von Appen --- And a third one. It often occurs on heavy disk access (e.g. running synth upgrade-system) FreeBSD ... 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r300409M: Wed May 25 22:39= :21 CEST 2016 ...:/usr/obj/usr/src/sys/GENERIC amd64 lock order reversal: 1st 0xfffffe03d06bc900 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3512 2nd 0xfffff800142ac400 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:281 stack backtrace: #0 0xffffffff80a9b7c0 at witness_debugger+0x70 #1 0xffffffff80a9b6b4 at witness_checkorder+0xe54 #2 0xffffffff80a452c2 at _sx_xlock+0x72 #3 0xffffffff80cfd74e at ufsdirhash_add+0x3e #4 0xffffffff80d004fa at ufs_direnter+0x4da #5 0xffffffff80d07b80 at ufs_rename+0xf60 #6 0xffffffff81002420 at VOP_RENAME_APV+0x100 #7 0xffffffff80b08928 at kern_renameat+0x4a8 #8 0xffffffff80ea6a2b at amd64_syscall+0x2db #9 0xffffffff80e86d9b at Xfast_syscall+0xfb lock order reversal: 1st 0xfffff80014d35240 ufs (ufs) @ /usr/src/sys/ufs/ufs/ufs_vnops.c:1157 2nd 0xfffffe03d06ce790 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:263 3rd 0xfffff80014f7c9a0 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498 stack backtrace: #0 0xffffffff80a9b7c0 at witness_debugger+0x70 #1 0xffffffff80a9b6b4 at witness_checkorder+0xe54 #2 0xffffffff80a155c6 at __lockmgr_args+0x4d6 #3 0xffffffff80cf8466 at ffs_lock+0xa6 #4 0xffffffff81002f30 at VOP_LOCK1_APV+0x100 #5 0xffffffff80b0b73a at _vn_lock+0x9a #6 0xffffffff80afbbb3 at vget+0x63 #7 0xffffffff80aee68c at vfs_hash_get+0xcc #8 0xffffffff80cf4200 at ffs_vgetf+0x40 #9 0xffffffff80cebcea at softdep_sync_buf+0xb3a #10 0xffffffff80cf9056 at ffs_syncvnode+0x256 #11 0xffffffff80cd05e7 at ffs_truncate+0x8a7 #12 0xffffffff80d08030 at ufs_rename+0x1410 #13 0xffffffff81002420 at VOP_RENAME_APV+0x100 #14 0xffffffff80b08928 at kern_renameat+0x4a8 #15 0xffffffff80ea6a2b at amd64_syscall+0x2db #16 0xffffffff80e86d9b at Xfast_syscall+0xfb --=20 You are receiving this mail because: You are the assignee for the bug.=