From owner-freebsd-current@freebsd.org Mon Jan 9 00:47:31 2017 Return-Path: Delivered-To: freebsd-current@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 05419CA2B68 for ; Mon, 9 Jan 2017 00:47:31 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-7.mit.edu (dmz-mailsec-scanner-7.mit.edu [18.7.68.36]) (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 A8A0C11A2 for ; Mon, 9 Jan 2017 00:47:30 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074424-673ff70000002ea5-6c-5872dd9904b3 Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id A8.70.11941.99DD2785; Sun, 8 Jan 2017 19:47:23 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id v090lK33003576; Sun, 8 Jan 2017 19:47:21 -0500 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v090lHUG021838 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 8 Jan 2017 19:47:20 -0500 Date: Sun, 8 Jan 2017 18:47:18 -0600 From: Benjamin Kaduk To: Anindya Mukherjee Cc: "freebsd-current@freebsd.org" Subject: Re: New Lock Order Reversal in 12.0? Message-ID: <20170109004717.GE8460@kduck.kaduk.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrFIsWRmVeSWpSXmKPExsUixG6nojv7blGEweWvYhaf1s9js5jz5gOT A5PHjE/zWTwe95xhC2CK4rJJSc3JLEst0rdL4Mr4Oncje8FlvoqjV64yNzCe4Oli5OSQEDCR eLfuGFsXIxeHkEAbk8TimbMYIZwNjBJXltxmgXCuMEnMufKWEaSFRUBF4snfJ+wgNhuQ3dB9 mRnEFhHQlfjyeBNYnFnAXqLtznawemGg+LUPK4BsDg5eAWOJrUe9QcJCAjESb6csYwWxeQUE JU7OfMIC0aolcePfSyaQcmYBaYnl/zhAwpwCsRJvnz5nArFFBZQlGmY8YJ7AKDALSfcsJN2z ELoXMDKvYpRNya3SzU3MzClOTdYtTk7My0st0jXXy80s0UtNKd3ECA5SF5UdjN093ocYBTgY lXh4X/gURQixJpYVV+YeYpTkYFIS5XWMKogQ4kvKT6nMSCzOiC8qzUktPsQowcGsJMK79wZQ OW9KYmVValE+TEqag0VJnPdSpnuEkEB6YklqdmpqQWoRTFaGg0NJgnfiHaBGwaLU9NSKtMyc EoQ0EwcnyHAeoOGzb4MMLy5IzC3OTIfIn2JUlBLnPQ6SEABJZJTmwfWCkohE9v6aV4ziQK8I 83qDrOABJiC47ldAg5mABgt65oMMLklESEk1ME6X4L/OWB7GlXBeWTructcz2yrf3o0bfzsp s8U/SG1i+XFzgk9OTtW9BU8tRTZxxthFHqiawsLz8ozFzdZe1mbxLfMnHGQsvufhb29xfFag l6D5shv1cmYtUSefu84QKu6ZcD167zbzV/GT0mKf3hOsvFAkV/Evj/2AU7Bjb3WVakXV3/Xv lFiKMxINtZiLihMBzEDAa/0CAAA= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 09 Jan 2017 00:47:31 -0000 On Mon, Jan 09, 2017 at 12:32:28AM +0000, Anindya Mukherjee wrote: > Hi, I'm running 12.0-current and noticed a LOR message from WITNESS which I couldn't find a report about. I looked at http://sources.zabbadoz.net/freebsd/lor.html, among other places. > > system details: > root@triskelion:~ # uname -a > FreeBSD triskelion 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r311461: Thu Jan 5 22:46:38 UTC 2017 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > root@triskelion:~ # freebsd-version > 12.0-CURRENT > > > WITNESS report: > lock order reversal: > 1st 0xfffff8002e8049a0 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2598 > 2nd 0xfffffe01e7ce9b40 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:277 > 3rd 0xfffff8002ec7b9a0 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2598 > stack backtrace: > #0 0xffffffff80aa6fd0 at witness_debugger+0x70 > #1 0xffffffff80aa6ed3 at witness_checkorder+0xde3 > #2 0xffffffff80a20c15 at __lockmgr_args+0x725 > #3 0xffffffff80d06fc5 at ffs_lock+0xa5 > #4 0xffffffff8101c0c0 at VOP_LOCK1_APV+0xe0 > #5 0xffffffff80b1a6aa at _vn_lock+0x9a > #6 0xffffffff80b0ac94 at vget+0x64 > #7 0xffffffff80afd19c at vfs_hash_get+0xcc > #8 0xffffffff80d02e5e at ffs_vgetf+0x3e > #9 0xffffffff80cf9787 at softdep_sync_buf+0xc37 > #10 0xffffffff80d07c51 at ffs_syncvnode+0x2a1 > #11 0xffffffff80d06e60 at ffs_fsync+0x20 > #12 0xffffffff8101b110 at VOP_FSYNC_APV+0xe0 > #13 0xffffffff80d0f2f0 at ufs_direnter+0x870 > #14 0xffffffff80d18050 at ufs_makeinode+0x5c0 > #15 0xffffffff80d13d7a at ufs_create+0x3a > #16 0xffffffff810199ca at VOP_CREATE_APV+0xda > #17 0xffffffff80b19f77 at vn_open_cred+0x2c7 > > This is based on the FreeBSD-12.0-CURRENT-amd64-20170105-r311461-memstick.img installer. Known issue? You do not think it looks like http://sources.zabbadoz.net/freebsd/lor/238.html ? -Ben