linux-kernel - Re: [PATCH 4.9 75/95] random: set up the NUMA crng instances after the CRNG is fully initialized

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]

Date:   Fri, 27 Apr 2018 11:44:33 +0200
From:   Ingo Molnar <mingo@...nel.org>
To:     "Theodore Y. Ts'o" <tytso@....edu>,
        Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
        gregkh@...uxfoundation.org, ben@...adent.org.uk,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        jannh@...gle.com, carnil@...ian.org
Subject: Re: [PATCH 4.9 75/95] random: set up the NUMA crng instances after
 the CRNG is fully initialized


* Theodore Y. Ts'o <tytso@....edu> wrote:

> On Thu, Apr 26, 2018 at 03:53:58PM +0900, Tetsuo Handa wrote:
> > Oh, pull request was already sent. Should be merged shortly.
> > 
> > https://marc.info/?l=linux-kernel&m=152472466201090&w=2
> 
> More testing, either before or after merging, would be greatly
> appreciated.  One of the challenges is that there are a lot of systems
> out there with different amounts of boot entropy available.  So this
> pull request was needed to help deal with issues on crazy big machines
> (CONFIG_NUMA) and crazy small laptops (old/small chromebooks
> repurposed to support Ubuntu and small ARM systems) --- neither of
> which I had access to when I was putting together the fixes to the
> random driver.
> 
> So any feedback before 4.17 gets released would be really helpful!
> 
> Thanks!!

I tested this upstream commit:

  665fa0000aed: Merge tag 'random_for_linus_stable' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random

... and the bug is fixed here too, my test machine is back to 'perfect'.

Thanks!

	Ingo