Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Feb 2016 18:28:29 -0500 (EST)
From:      Benjamin Kaduk <kaduk@MIT.EDU>
To:        Eax Melanhovich <afiskon@devzen.ru>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Lock order reversal in CURRENT
Message-ID:  <alpine.GSO.1.10.1602241827120.26829@multics.mit.edu>
In-Reply-To: <20160224153007.79bcf4ec@fujitsu>
References:  <20160224153007.79bcf4ec@fujitsu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 24 Feb 2016, Eax Melanhovich wrote:

> Hello.
>
> Yesterday I built a kernel and world using master branch (6a8922d3) of
> FreeBSD GitHub repository (a mirror of SVN as I understand?). Today I
> got a "lock order reversal" report:
>
> http://i.imgur.com/jDZ4A3O.png
>
> According to this FAQ it could be a sign of a deadlock:
>
> https://www.freebsd.org/doc/faq/troubleshoot.html#idp63366608
>
> Do I have to report this issue anywhere except freebsd-current@ ?

That particular one, though not in the table at
http://sources.zabbadoz.net/freebsd/lor.html, seems similar enough to a
ufs/devfs entry that shows up very often and is harmless, to make me think
that just the mail you have sent is quite sufficient.

Thanks,

Ben Kaduk



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1602241827120.26829>