[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFxkdArLwrG8x6fNtLUfHedKrH_0d97V6UEzOCBgK8Shkir9pQ@mail.gmail.com>
Date: Tue, 1 May 2018 17:35:56 -0500
From: Justin Forbes <jmforbes@...uxtx.org>
To: "Theodore Y. Ts'o" <tytso@....edu>,
Justin Forbes <jmforbes@...uxtx.org>,
Jeremy Cline <jeremy@...ine.org>,
Sultan Alsawaf <sultanxda@...il.com>,
Pavel Machek <pavel@....cz>,
LKML <linux-kernel@...r.kernel.org>, Jann Horn <jannh@...gle.com>
Subject: Re: Linux messages full of `random: get_random_u32 called from`
On Tue, May 1, 2018 at 7:55 AM, Theodore Y. Ts'o <tytso@....edu> wrote:
> On Tue, May 01, 2018 at 06:52:47AM -0500, Justin Forbes wrote:
>>
>> We have also had reports that Fedora users are seeing this on Google
>> Compute Engine.
>
> Can you reproduce this yourself? If so, could you confirm that
> removing the dracut-fips package makes the problem go away for you?
>
I have not reproduced in GCE myself. We did get some confirmation
that removing dracut-fips does make the problem less dire (but I
wouldn't call a 4 minute boot a win, but booting in 4 minutes is
better than not booting at all). Specifically systemd calls libgcrypt
before it even opens the log with fips there, and this is before
virtio-rng modules could even load. Right now though, we are looking
at pretty much any possible options as the majority of people are
calling for me to backout the patches completely from rawhide.
Powered by blists - more mailing lists