From owner-freebsd-current@FreeBSD.ORG Sun Jan 30 10:14:04 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C0E816A4E9; Sun, 30 Jan 2005 10:14:04 +0000 (GMT) Received: from dglawrence.com (dsl-230-156.ipns.com [209.210.230.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93F7D43D2D; Sun, 30 Jan 2005 10:14:03 +0000 (GMT) (envelope-from dg@dglawrence.com) Received: from opteron.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.13.1/8.13.1) with ESMTP id j0UAE3dk087982; Sun, 30 Jan 2005 02:14:03 -0800 (PST) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by opteron.dglawrence.com (8.13.1/8.13.1/Submit) id j0UAE3aD087981; Sun, 30 Jan 2005 02:14:03 -0800 (PST) (envelope-from dg@dglawrence.com) Date: Sun, 30 Jan 2005 02:14:03 -0800 From: "David G. Lawrence" To: Kris Kennaway Message-ID: <20050130101403.GM48777@opteron.dglawrence.com> References: <20050130025217.GA32612@xor.obsecurity.org> <20050130075422.GL48777@opteron.dglawrence.com> <20050130093527.GA89923@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050130093527.GA89923@xor.obsecurity.org> cc: alc@freeBSD.org cc: current@freeBSD.org Subject: Re: do_execve() finding vmspace_destroyed set under load X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jan 2005 10:14:04 -0000 > > > Needless to say, the scripts get pretty unhappy when they're summarily > > > aborted. What is the cause of this? > > > > There are many reasons why an exec can fail - you'd need to collect > > more info to be able to say specifically. Speaking generally, the above > > code happens because something failed after the process's address space > > had been cleared, so there is no process executable image to return > > to. The only thing to do in that case is to kill off the process. If > > you're only seeing the problem under load, it is probably indicating > > that your running out of a kernel VM pool of some kind. > > Any suggestions on what to look at to try and debug this further? The first thing to do is to add some kernel printf's to do_execve() in each of the 'if (error)' cases to determine where the error is occuring. It's probably not worth putting them in cases prior to the 'loop through the list of image activators', since the vmspace isn't destroyed until then. Once you've done that, the cause of the problem should become obvious. -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 TeraSolutions, Inc. - http://www.terasolutions.com - (888) 346 7175 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities.