Re: Lock order reversal in CURRENT

[Benjamin Kaduk]

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
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: lock order reversal under -current

[John Baldwin]

On 28-Feb-01 Michael Reifenberger wrote:
 Hi,
 with -current sources (as of -now) I get during startup:
 
 lock order reversal
  1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:625
  2nd 0xc0306840 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:940
  3rd 0xcbd20a0c vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:949
  32
 
 Is that bad?

Yes and no.  It's a bug yes, but it has probably been around since at least
4.4BSD, so you can ignore it for now.

-- 

John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message