> This fixes -current on my machines (i386 UP and SMP).
Confirmed for UP i686.
> Should be in the clear now. asmodia has seen a lock reversal between
> the process lock and uidinfo lock, but I can't reproduce it. You
> probably want to remove the kernel option WITNESS_DDB if you have it
> it enabled.
Same here. I get the (now usual):
lock order reversal
1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:644
2nd 0xc0299bc0 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:940
3rd 0xc6595dac vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:949
then later:
lock order reversal
1st lockmgr last acquired @ ../../kern/kern_lock.c:505
2nd 0xc02824a0 uidinfo hash @ ../../kern/kern_resource.c:727
3rd 0xc0280460 lockmgr @ ../../kern/kern_lock.c:239
and a few seconds later:
lock order reversal
1st lockmgr last acquired @ ../../kern/kern_lock.c:505
2nd 0xc0ac9e1c uidinfo struct @ ../../kern/kern_resource.c:781
3rd 0xc0280460 lockmgr @ ../../kern/kern_lock.c:239
Bye,
Andrea
--
The best things in life are free, but the
expensive ones are still worth a look.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
