[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whfPwei+yf9vBgfSuG5HDtiYmt3nOu9Js+vkTYSrMf2ow@mail.gmail.com>
Date: Mon, 16 Sep 2019 18:41:36 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Matthew Garrett <mjg59@...f.ucam.org>
Cc: "Ahmed S. Darwish" <darwish.07@...il.com>,
"Theodore Y. Ts'o" <tytso@....edu>, Willy Tarreau <w@....eu>,
Vito Caputo <vcaputo@...garu.com>,
Lennart Poettering <mzxreary@...inter.de>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Jan Kara <jack@...e.cz>, Ray Strode <rstrode@...hat.com>,
William Jon McCann <mccann@....edu>,
"Alexander E. Patrakov" <patrakov@...il.com>,
zhangjs <zachary@...shancloud.com>, linux-ext4@...r.kernel.org,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: Linux 5.3-rc8
On Mon, Sep 16, 2019 at 6:24 PM Matthew Garrett <mjg59@...f.ucam.org> wrote:
>
> Exactly the scenario where you want getrandom() to block, yes.
It *would* block. Just not forever.
And btw, the whole "generate key at boot when nothing else is going
on" is already broken, so presumably nobody actually does it.
See why I'm saying "hypothetical"? You're doing it again.
> >Then you have to ignore the big warning too.
>
> The big warning that's only printed in dmesg?
Well, the patch actually made getrandom() return en error too, but you
seem more interested in the hypotheticals than in arguing actualities.
Linus
Powered by blists - more mailing lists