linux-kernel - Re: [PATCH] make execve(NULL) re-execute current binary

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: <20090630133354.518be0ec@lxorguk.ukuu.org.uk>
Date:	Tue, 30 Jun 2009 13:33:54 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Denys Vlasenko <vda.linux@...glemail.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Mike Frysinger <vapier@...too.org>
Subject: Re: [PATCH] make execve(NULL) re-execute current binary

> The behavior of execve(NULL) is not undefined. It returns EFAULT.
> The idea was that application will do:

That depends what you have mapped at address zero and if your platform
supports EFAULT reporting for address zero. It isn't a reliable
assumption.

Alan
--
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/