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
| ||
|
Message-ID: <YzLCy2rVIBebeMrB@zx2c4.com> Date: Tue, 27 Sep 2022 11:30:51 +0200 From: "Jason A. Donenfeld" <Jason@...c4.com> To: Kees Cook <keescook@...omium.org> Cc: linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, Ard Biesheuvel <ardb@...nel.org>, Alexander Potapenko <glider@...gle.com>, Marco Elver <elver@...gle.com>, Dmitry Vyukov <dvyukov@...gle.com>, kasan-dev@...glegroups.com, linux-hardening@...r.kernel.org Subject: Re: [PATCH] random: split initialization into early arch step and later non-arch step On Tue, Sep 27, 2022 at 10:34:16AM +0200, Jason A. Donenfeld wrote: > > > Yes, we could maybe *change* to using init_utsname if we wanted. That > > > seems kind of different though. So I'd prefer that to be a different > > > patch, which would require looking at the interaction with early > > > hostname setting and such. If you want to do that work, I'd certainly > > > welcome the patch. > > > > Er, isn't that _WAY_ later? Like, hostname isn't set until sysctls up > > and running, etc. I haven't actually verified 100% but it looks like > > current->utsname is exactly init_utsname currently. > > If init_utsname()==utsname() and all is fine, can you please send a > patch atop random.git adjusting that and explaining why? I would > happily take such a patch. If your suspicion is correct, it would make > a most welcome improvement. https://lore.kernel.org/lkml/20220927092920.1559685-1-Jason@zx2c4.com
Powered by blists - more mailing lists