From owner-freebsd-bugs@freebsd.org Fri Jun 16 17:02:14 2017 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 A9A01C786A1 for ; Fri, 16 Jun 2017 17:02:14 +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 8ED99322C for ; Fri, 16 Jun 2017 17:02:14 +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 v5GH2E5l068243 for ; Fri, 16 Jun 2017 17:02:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 209816] [lor] lock order reversal with devfs, tmpfs and ufs Date: Fri, 16 Jun 2017 17:02:14 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ml@netfence.it 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: cc 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.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jun 2017 17:02:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209816 ml@netfence.it changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ml@netfence.it --- Comment #1 from ml@netfence.it --- Hello. I've just seen the same on a 10.3p18/amd64: lock order reversal: 1st 0xfffff803b3908a28 tmpfs (tmpfs) @ /usr/src/sys/kern/vfs_mount.c:848 2nd 0xfffff803b3908c98 ufs (ufs) @ /usr/src/sys/fs/nullfs/null_vnops.c:670 KDB: stack backtrace: #0 0xffffffff804c72b0 at kdb_backtrace+0x60 #1 0xffffffff804e7204 at witness_checkorder+0xe24 #2 0xffffffff80468a79 at __lockmgr_args+0x9d9 #3 0xffffffff806b2162 at ffs_lock+0x92 #4 0xffffffff8077ad5c at VOP_LOCK1_APV+0xfc #5 0xffffffff803c2dd0 at null_lock+0xe0 #6 0xffffffff8077ad5c at VOP_LOCK1_APV+0xfc #7 0xffffffff80547492 at _vn_lock+0xd2 #8 0xffffffff803c2010 at nullfs_root+0x50 #9 0xffffffff805306d8 at vfs_donmount+0x13b8 #10 0xffffffff8052f2ff at sys_nmount+0x4f #11 0xffffffff80712f3c at amd64_syscall+0x2ac #12 0xffffffff806f6b0b at Xfast_syscall+0xfb lock order reversal: 1st 0xfffff803a337c2d8 tmpfs (tmpfs) @ /usr/src/sys/kern/vfs_mount.c:848 2nd 0xfffff8024f106a28 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2253 KDB: stack backtrace: #0 0xffffffff804c72b0 at kdb_backtrace+0x60 #1 0xffffffff804e7204 at witness_checkorder+0xe24 #2 0xffffffff80468a79 at __lockmgr_args+0x9d9 #3 0xffffffff80528a5c at vop_stdlock+0x3c #4 0xffffffff8077ad5c at VOP_LOCK1_APV+0xfc #5 0xffffffff80547492 at _vn_lock+0xd2 #6 0xffffffff805387e7 at vget+0x67 #7 0xffffffff8038e8cd at devfs_allocv+0xfd #8 0xffffffff8038e353 at devfs_root+0x43 #9 0xffffffff805306d8 at vfs_donmount+0x13b8 #10 0xffffffff8052f2ff at sys_nmount+0x4f #11 0xffffffff80712f3c at amd64_syscall+0x2ac #12 0xffffffff806f6b0b at Xfast_syscall+0xfb The second one looks like and old friend: http://sources.zabbadoz.net/freebsd/lor/280.html I couldn't fine the first one on that list, though. This happened while running Poudriere on a full UFS+SU (no ZFS) system. In fact Poudriere has brough my box to a complete hang several times (forci= ng an hardware reset) and that's why I enabled WITNESS, INVARIANTS, etc... After such an hang, the system is very likely to panic over and over again until I boot into single user mode and "fsck -y" every filesystem (includin= g a full fsck after replaying the journal on UFS+SU+J partitions). On another run only the second LOR showed up without the first. --=20 You are receiving this mail because: You are the assignee for the bug.=