From owner-freebsd-current Tue Jun 18 12:48:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 6FCFD37B404 for ; Tue, 18 Jun 2002 12:48:28 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 3ECCFAE28D; Tue, 18 Jun 2002 12:48:28 -0700 (PDT) Date: Tue, 18 Jun 2002 12:48:28 -0700 From: Alfred Perlstein To: Nate Lawson Cc: current@freebsd.org Subject: Re: Suggested fixes for uidinfo "would sleep" messages Message-ID: <20020618194828.GC12139@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Nate Lawson [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