* Nate Lawson <[EMAIL PROTECTED]> [020618 12:17] wrote: > As with others on the list, I've been getting a lot of witness complaints: > > ../../../vm/uma_core.c:1327: could sleep with "process lock" locked from > ../../../kern/kern_prot.c:511 > ../../../vm/uma_core.c:1327: could sleep with "process lock" locked from > ../../../kern/kern_prot.c:613 > > Basically, every time cron runs, it does a setuid() or seteuid(), which > calls change_ruid or change_euid which call uifree and uifind (which does > the malloc with M_WAITOK while holding PROC_LOCK). ... > Is anyone else working on a fix?
The code should not be holding proc locks over ui*() calls. -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message