From: "George Spelvin" <linux@horizon.com>
Subject: Re: [PATCH, RFC] random: introduce getrandom(2) system call
Date: 23 Jul 2014 07:52:53 -0400
Message-ID: <20140723115253.9808.qmail@ns.horizon.com>
References: <1406108835.2603.144733749.2407B407@webmail.messagingengine.com>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux@horizon.com
To: hannes@stressinduktion.org, tytso@mit.edu
In-Reply-To: <1406108835.2603.144733749.2407B407@webmail.messagingengine.com>
Sender: linux-crypto-owner@vger.kernel.org

I keep wishing for a more general solution.  For example, some way to
have a "spare" extra fd that could be accessed with a special O_NOFAIL
flag.

That would allow any number of library functions to not fail, such as
logging from nasty corner cases.

But you'd have to provide one per thread, and block non-fatal signals
while it was open, so you don't get reentrancy problems.  Ick.


This overly-specialized system call (and worse yet, a blocking
system call that you can't put into a poll() loop) just feels ugly
to me.  Is it *absolutely* necessary?

For example, how about simply making getentropy() a library function that
aborts if it can't open /dev/urandom?  If you're suffering fd exhaustion,
you're being DoSed already.