Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220707000021.504308-1-Jason@zx2c4.com> <2603a1c4-ef5d-7719-b458-e70da180b878@infradead.org>
In-Reply-To: <2603a1c4-ef5d-7719-b458-e70da180b878@infradead.org>
From:   "Jason A. Donenfeld" <Jason@zx2c4.com>
Date:   Thu, 7 Jul 2022 02:14:23 +0200
Message-ID: <CAHmME9oeyPy5EEXU094xSEBDQ1xcqAgVbAihgS7_kEWCnw1kww@mail.gmail.com>
Subject: Re: [PATCH] random: remove "nordrand" flag in favor of "random.trust_cpu"
To:     Randy Dunlap <rdunlap@infradead.org>
Cc:     LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>,
        "Theodore Ts'o" <tytso@mit.edu>, "H . Peter Anvin" <hpa@zytor.com>,
        Borislav Petkov <bp@suse.de>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hi Randy,

On Thu, Jul 7, 2022 at 2:12 AM Randy Dunlap <rdunlap@infradead.org> wrote:
> > However, x86 RDRAND does have a history of being occassionally
>
>                                                    occasionally
>
> > automatically disabling "nordrand" if we detect it's problematic.
> ?  I.e., disabling RDRAND and RDSEED.
> > -      * The nordrand option can clear X86_FEATURE_RDRAND, so check for
> > +      * The self test can clear X86_FEATURE_RDRAND, so check for
>
> Preferably:    self-test

Thanks. Fixing all of those.

Jason