linux-kernel - Re: [PATCH] random: use init_utsname() instead of utsname()

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <202209270717.E8B133F28@keescook>
Date:   Tue, 27 Sep 2022 07:17:13 -0700
From:   Kees Cook <keescook@...omium.org>
To:     "Jason A. Donenfeld" <Jason@...c4.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH] random: use init_utsname() instead of utsname()

On Tue, Sep 27, 2022 at 11:29:20AM +0200, Jason A. Donenfeld wrote:
> Rather than going through the current-> indirection for utsname, at this
> point in boot, init_utsname()==utsname(), so just use it directly that
> way. Additionally, init_utsname() appears to be available nearly always,
> so move it into random_init_early().
> 
> Suggested-by: Kees Cook <keescook@...omium.org>
> Signed-off-by: Jason A. Donenfeld <Jason@...c4.com>

Reviewed-by: Kees Cook <keescook@...omium.org>

-- 
Kees Cook