From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 999 invoked by alias); 7 Sep 2017 11:27:58 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 984 invoked by uid 89); 7 Sep 2017 11:27:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=H*MI:mid, H*M:mid X-HELO: albireo.enyo.de From: Florian Weimer To: Andreas Schwab Cc: libc-alpha@sourceware.org Subject: Re: [PATCH] Use execveat syscall in fexecve References: Date: Thu, 07 Sep 2017 11:27:00 -0000 In-Reply-To: (Andreas Schwab's message of "Thu, 07 Sep 2017 11:06:26 +0200") Message-ID: <87bmmmlpe1.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SW-Source: 2017-09/txt/msg00292.txt.bz2 * Andreas Schwab: > By using execveat we no longer depend on /proc. The execveat syscall was > introduced in 3.19, except for a few late comers. Ideally, this should have a test that executing =E2=80=9C/bin/sh -c true=E2= =80=9D works, both with an O_PATH descriptor and a regular descriptor. The implementation itself (including the AT_EMPTY_PATH flag) and the __ASSUME_EXECVEAT conditions look good to me.