Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758187AbaGQWfH (ORCPT ); Thu, 17 Jul 2014 18:35:07 -0400 Received: from mail.lang.hm ([64.81.33.126]:45882 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757592AbaGQWfF (ORCPT ); Thu, 17 Jul 2014 18:35:05 -0400 X-Greylist: delayed 775 seconds by postgrey-1.27 at vger.kernel.org; Thu, 17 Jul 2014 18:35:05 EDT Date: Thu, 17 Jul 2014 15:21:41 -0700 (PDT) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: Andy Lutomirski cc: Mark Kettenis , "Theodore Ts'o" , linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, beck@openbsd.org Subject: Re: [PATCH, RFC] random: introduce getrandom(2) system call In-Reply-To: <53C83383.4040507@amacapital.net> Message-ID: References: <201407171848.s6HImBb4027900@glazunov.sibelius.xs4all.nl> <53C83383.4040507@amacapital.net> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 17 Jul 2014, Andy Lutomirski wrote: > Can we please have a mode in which getrandom(2) can neither block nor > fail? If that gets added, then this can replace things like AT_RANDOM. If a call to get random data isn't allowed to either block or fail, what is it supposed to return if there isn't random data available? David Lang -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/