Date: Tue, 18 Jun 2002 12:48:28 -0700 From: Alfred Perlstein <bright@mu.org> To: Nate Lawson <nate@root.org> Cc: current@freebsd.org Subject: Re: Suggested fixes for uidinfo "would sleep" messages Message-ID: <20020618194828.GC12139@elvis.mu.org> In-Reply-To: <Pine.BSF.4.21.0206181226040.10665-100000@root.org> References: <Pine.BSF.4.21.0206181226040.10665-100000@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Nate Lawson <nate@root.org> [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 [alfred@freebsd.org] '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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020618194828.GC12139>