From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-75315-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 55911 invoked by alias); 29 Nov 2016 17:53:28 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 55901 invoked by uid 89); 29 Nov 2016 17:53:28 -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*r:sk:zimbra., Hx-spam-relays-external:sk:zimbra., H*RU:sk:zimbra., HX-HELO:sk:zimbra.
X-HELO: zimbra.cs.ucla.edu
Subject: Re: [PATCH v7] getrandom system call wrapper [BZ #17252]
To: Zack Weinberg <zackw@panix.com>, Florian Weimer <fweimer@redhat.com>
References: <3dd5d3b8-c196-98fb-1671-90cd90ab90c7@redhat.com>
 <244f578c-889a-a4cf-c686-bb2a5e49cca1@panix.com>
 <d14e4419-c1e5-ac38-9caa-688481a26464@redhat.com>
 <2d175242-1a82-9410-d01e-682ab4d9081e@panix.com>
 <c30852c5-9a52-83ea-4af1-310f97febccd@redhat.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>
 <CAKCAbMhUMgH+H6TU64apOvRgQ51BrHr77FEVH2Fr-bzchz7EDw@mail.gmail.com>
Cc: Torvald Riegel <triegel@redhat.com>, Szabolcs Nagy
 <szabolcs.nagy@arm.com>, Adhemerval Zanella <adhemerval.zanella@linaro.org>,
 nd <nd@arm.com>, GNU C Library <libc-alpha@sourceware.org>
From: Paul Eggert <eggert@cs.ucla.edu>
Message-ID: <d27c4a81-a81a-3cb1-aee4-5e3f6e9fa715@cs.ucla.edu>
Date: Tue, 29 Nov 2016 17:53: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: <CAKCAbMhUMgH+H6TU64apOvRgQ51BrHr77FEVH2Fr-bzchz7EDw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2016-11/txt/msg01068.txt.bz2

On 11/29/2016 07:54 AM, Zack Weinberg wrote:
> Would it make sense for getentropy
> to loop internally rather than returning a short read?

FWIW, that is what I was planning when implementing a more-portable 
version of getentropy (I guess that's its name now?) for Gnulib, after 
the API settles down. Gnulib-using applications typically need a small 
number of random bytes. I don't want to worry about modifying these apps 
to take into account the possibility of waiting indefinitely due to a 
bug in the hardware or operating system. If such a wait occurs, it's OK 
with me to just say "fix your platform".