From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 55194 invoked by alias); 29 Nov 2016 19:37:27 -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 55174 invoked by uid 89); 29 Nov 2016 19:37:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=H*M:593a, H*M:8b3b X-HELO: zimbra.cs.ucla.edu Subject: Re: [PATCH v7] getrandom system call wrapper [BZ #17252] To: Florian Weimer , Zack Weinberg References: <3dd5d3b8-c196-98fb-1671-90cd90ab90c7@redhat.com> <244f578c-889a-a4cf-c686-bb2a5e49cca1@panix.com> <2d175242-1a82-9410-d01e-682ab4d9081e@panix.com> <1479319342.7146.1143.camel@localhost.localdomain> <950ffaeb-8984-7840-e495-12442f821c9c@linaro.org> <1479387147.7146.1147.camel@localhost.localdomain> <582EBBB5.80309@arm.com> <1479478867.7146.1167.camel@localhost.localdomain> <9357f19f-be56-0c1d-4192-260b485c3767@redhat.com> <1479485050.7146.1201.camel@localhost.localdomain> <1682bf93-5fbc-80db-1348-e5b8973a59f2@redhat.com> <1480427804.14990.24.camel@redhat.com> <27d946d1-ef23-df50-8061-cbada2dea2e9@redhat.com> <1480433030.14990.34.camel@redhat.com> <35a658d5-517f-c49b-de47-fdf3192034e2@redhat.com> Cc: Torvald Riegel , Szabolcs Nagy , Adhemerval Zanella , nd , GNU C Library From: Paul Eggert Message-ID: <3c6a8a52-8b3b-593a-2916-048dc3796f1c@cs.ucla.edu> Date: Tue, 29 Nov 2016 19:37:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2016-11/txt/msg01074.txt.bz2 On 11/29/2016 10:11 AM, Florian Weimer wrote: > How are you going to avoid interposing the implementation in glibc? That will depend on how glibc is implemented. Simplest might be to use compile-time interposition, which is common in Gnulib. E.g., Gnulib would supply its own getentropy.h which does "#define getentropy rpl_getentropy", so that Gnulib-using applications always call rpl_getentropy from the linker's point of view. This sort of thing is OK for Gnulib, as it's not intended to be a separate library.