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] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 09 Feb 2019 10:19:01 -0800
From:   James Bottomley <James.Bottomley@...senPartnership.com>
To:     Mikael Pettersson <mikpelinux@...il.com>,
        Linux SPARC Kernel Mailing List 
        <sparclinux@...r.kernel.org>, linux-block@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [5.0-rc5 regression] "scsi: kill off the legacy IO path" causes
 5 minute delay during boot on Sun Blade 2500

On Sat, 2019-02-09 at 18:04 +0100, Mikael Pettersson wrote:
> 4.20 and earlier kernels boot fine on my Sun Blade 2500 (UltraSPARC
> IIIi), but the 5.0-rc kernels consistently experience a 5 minute
> delay
> late during boot, after enabling networking but before allowing user
> logins.  E.g. 5.0-rc5 dmesg has:
> 
> [Fri Feb  8 17:13:17 2019] random: dbus-daemon: uninitialized urandom
> read (12 bytes read)
> [Fri Feb  8 17:18:14 2019] random: crng init done

I've had the same problem on several of my test systems.  Are you sure
it's not this bug report:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912087

?

The solution for me was to install the haveged package which does
active entropy gathering during boot and can make /dev/urandom
available much earlier.

> During this interval the machine answers pings but won't allow user
> logins either on the console or over the network.
> 
> A git bisect identified commit
> f664a3cc17b7d0a2bc3b3ab96181e1029b0ec0e6
> Author: Jens Axboe <axboe@...nel.dk>
> Date:   Thu Nov 1 16:36:27 2018 -0600
> 
>     scsi: kill off the legacy IO path
> 
> as the point where this 5m delay was introduced.

I think the reason for this is that the block mq path doesn't feed the
kernel entropy pool correctly, hence the need to install an entropy
gatherer for systems that don't have other good random number sources.

James

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ