lock order reversal under -current

2001-02-28 Thread Michael Reifenberger

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?

Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS


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



RE: lock order reversal under -current

2001-02-28 Thread 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