lock order reversal under -current

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!

RE: lock order reversal under -current

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 @