lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 7 Jan 2020 15:43:32 -0500 From: "Theodore Y. Ts'o" <tytso@....edu> To: Andy Lutomirski <luto@...nel.org> Cc: LKML <linux-kernel@...r.kernel.org>, Linux API <linux-api@...r.kernel.org>, Kees Cook <keescook@...omium.org>, "Jason A. Donenfeld" <Jason@...c4.com>, "Ahmed S. Darwish" <darwish.07@...il.com>, Lennart Poettering <mzxreary@...inter.de>, "Eric W. Biederman" <ebiederm@...ssion.com>, "Alexander E. Patrakov" <patrakov@...il.com>, Michael Kerrisk <mtk.manpages@...il.com>, Willy Tarreau <w@....eu>, Matthew Garrett <mjg59@...f.ucam.org>, Ext4 Developers List <linux-ext4@...r.kernel.org>, linux-man <linux-man@...r.kernel.org>, Stephan Mueller <smueller@...onox.de> Subject: Re: [PATCH v3 2/8] random: Add a urandom_read_nowait() for random APIs that don't warn On Mon, Dec 23, 2019 at 12:20:45AM -0800, Andy Lutomirski wrote: > /dev/random and getrandom() never warn. Split the meat of > urandom_read() into urandom_read_nowarn() and leave the warning code > in urandom_read(). > > This has no effect on kernel behavior, but it makes subsequent > patches more straightforward. It also makes the fact that > getrandom() never warns more obvious. > > Signed-off-by: Andy Lutomirski <luto@...nel.org> Applied, thanks. - Ted
Powered by blists - more mailing lists