lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1217597717.4684.1.camel@twins>
Date:	Fri, 01 Aug 2008 15:35:17 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Halesh S <halesh.s@...ia.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Need inforamtion on execve(2) on ENOMEM

On Fri, 2008-08-01 at 13:30 +0000, Halesh S wrote:
> Hi,
> 
> I need a bit information regarding execve(2) sys call failure on no memory.
> 
> when execve(2) exits with ENOMEM, it will fail to return back to the calling 
> program as it receives the SIGKILL from the kernel.
> 
> Is it a right behavior that execve() will not return to calling 
> program on ENOMEM. As I understood execve(2) will not return only on success.
> 
> As errno will be lost, its very diffcult to judge execve(2) status.
> 
> If not expected behaviour,  I can provide a testcase for this.
> 
> Please let me about this.

It only does the SIGKILL bit when it runs out of memory after the old
programm is dead and the new programm isn't quite running yet.

So there is no calling programm to return to.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ