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 linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 30 Jan 2022 23:11:22 +0100 From: "Jason A. Donenfeld" <Jason@...c4.com> To: Dominik Brodowski <linux@...inikbrodowski.net> Cc: "Theodore Ts'o" <tytso@....edu>, LKML <linux-kernel@...r.kernel.org>, Linux Crypto Mailing List <linux-crypto@...r.kernel.org> Subject: Re: [PATCH 2/2] random: only call crng_finalize_init() for primary_crng Thanks, I'll apply this. I do wonder, though, do we have locking concerns around crng_init transitioning from 1 to 2, or with calls to crng_need_final_init? For example, can crng_reseed be called at the same time as rand_initialize? Or are we still single core at this point in the boot sequence? I don't think that this patch changes anything from that perspective, which is why it seems reasonable to apply, but I do wonder. Jason
Powered by blists - more mailing lists