Date: Mon, 16 May 2016 07:44:32 +0000 From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Kurt Jaeger <lists@opsec.eu> Cc: Will Brokenbourgh <will_brokenbourgh@yahoo.com>, freebsd-current@freebsd.org Subject: Re: Lock order reversal errors during boot Message-ID: <BA4A43C5-5BCD-4B7B-B3C8-416C15AA2727@lists.zabbadoz.net> In-Reply-To: <20160515074404.GF15034@home.opsec.eu> References: <6b965a16-a6c7-a063-3c2a-7c577c2f9b56@yahoo.com> <20160515074404.GF15034@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 15 May 2016, at 07:44 , Kurt Jaeger <lists@opsec.eu> wrote: >=20 > Hi! >=20 >> I am seeing 'lock order reversal' errors during boot on 11-CURRENT -=20= >> r298793. A sample error: >>=20 >> lock order reversal: >> 1st 0xfffff8011280d068 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498 >> 2nd 0xfffffe01ca539400 bufwait (bufwait) @=20 >> /usr/src/sys/ufs/ffs/ffs_vnops.c:263 >> 3rd 0xfffff80112a23b78 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498 >> stack backtrace: >> #0 0xffffffff80a94bf0 at witness_debugger+0x70 >> #1 0xffffffff80a94ae4 at witness_checkorder+0xe54 >> #2 0xffffffff80a0fdd6 at __lockmgr_args+0x4d6 >> #3 0xffffffff80ce9626 at ffs_lock+0xa6 >> [...snip...] >>=20 >> I'm not sure if this is even something I should report, but better = safe=20 >> than sorry, yes? >=20 > Yes, and there's even a page to compare your LOR against other ones: >=20 > http://sources.zabbadoz.net/freebsd/lor.html >=20 > Can you try if you find your LOR there ? If not, can you add it > to that page ? No he can=E2=80=99t and I haven=E2=80=99t in years either. Searching = bugs might however be a good idea; there is a LOR category or tag = somewhere. /bz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BA4A43C5-5BCD-4B7B-B3C8-416C15AA2727>