Date: Sun, 30 Jan 2005 02:14:03 -0800 From: "David G. Lawrence" <dg@dglawrence.com> To: Kris Kennaway <kris@obsecurity.org> Cc: current@freeBSD.org Subject: Re: do_execve() finding vmspace_destroyed set under load Message-ID: <20050130101403.GM48777@opteron.dglawrence.com> In-Reply-To: <20050130093527.GA89923@xor.obsecurity.org> References: <20050130025217.GA32612@xor.obsecurity.org> <20050130075422.GL48777@opteron.dglawrence.com> <20050130093527.GA89923@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050130101403.GM48777>