From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9879 invoked by alias); 11 Sep 2017 20:59:38 -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 9863 invoked by uid 89); 11 Sep 2017 20:59:37 -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= X-HELO: albireo.enyo.de From: Florian Weimer To: Joseph Myers Cc: Adhemerval Zanella , Subject: Re: [PATCH v2] Use execveat syscall in fexecve References: <87bmmmlpe1.fsf@mid.deneb.enyo.de> <2a21b0d6-5f62-a711-2b4a-616ebb798963@linaro.org> Date: Mon, 11 Sep 2017 20:59:00 -0000 In-Reply-To: (Joseph Myers's message of "Mon, 11 Sep 2017 20:38:16 +0000") Message-ID: <87vakpymrw.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2017-09/txt/msg00470.txt.bz2 * Joseph Myers: > We have the ENOSYS code there and the subsequent fallback that will > eventually need cleaning up *anyway*. Having the __ASSUME_* macro makes > it obvious in future exactly what changes should be made for the cleanup > and exactly when it is possible to do that cleanup. I think having such > macros for any case with fallback code that can be cleaned up in future is > a good idea for that reason. Agreed. As long as there is an expectation that we will eventually bump the minimum kernel requirement, __ASSUME_* macros are the way to go.