Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Jan 2005 01:35:27 -0800
From:      Kris Kennaway <kris@obsecurity.org>
To:        "David G. Lawrence" <dg@dglawrence.com>
Cc:        Kris Kennaway <kris@obsecurity.org>
Subject:   Re: do_execve() finding vmspace_destroyed set under load
Message-ID:  <20050130093527.GA89923@xor.obsecurity.org>
In-Reply-To: <20050130075422.GL48777@opteron.dglawrence.com>
References:  <20050130025217.GA32612@xor.obsecurity.org> <20050130075422.GL48777@opteron.dglawrence.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--6c2NcOVqGQ03X4Wi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jan 29, 2005 at 11:54:22PM -0800, David G. Lawrence wrote:
> > I'm seeing the following code in do_execve() frequently being
> > triggered when scripts are executed on my SMP machine under load:
> >=20
> >         if (imgp->vmspace_destroyed) {
> >                  /* sorry, no more process anymore. exit gracefully */
> > #ifdef MAC
> >                 mac_execve_exit(imgp);
> >                 if (interplabel !=3D NULL)
> >                         mac_vnode_label_free(interplabel);
> > #endif
> >                 exit1(td, W_EXITCODE(0, SIGABRT));
> >                 /* NOT REACHED */
> >                 error =3D 0;
> >         }
> >=20
> > Needless to say, the scripts get pretty unhappy when they're summarily
> > aborted.  What is the cause of this?
>=20
>    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?

Kris

--6c2NcOVqGQ03X4Wi
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFB/KpfWry0BWjoQKURApj/AJ45sA/eM9CwH98NmhbzNc1I3X0MTgCcDZwJ
rNP6NFcHtFA7FcMJPk7CNsc=
=xeHI
-----END PGP SIGNATURE-----

--6c2NcOVqGQ03X4Wi--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050130093527.GA89923>