linux-kernel - Re: 5.18.1 has thousands of similar lines in dmesg with CONFIG_WARN_ALL_UNSEEDED

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]

Message-ID: <87tu963ii2.fsf@jogness.linutronix.de>
Date:   Mon, 30 May 2022 21:58:53 +0206
From:   John Ogness <john.ogness@...utronix.de>
To:     Toralf Förster <toralf.foerster@....de>,
        Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: 5.18.1 has thousands of similar lines in dmesg with
 CONFIG_WARN_ALL_UNSEEDED_RANDOM=y

On 2022-05-30, Toralf Förster <toralf.foerster@....de> wrote:
> On 5/30/22 11:24, Toralf Förster wrote:
>> This deletes the early boot messages in dmesg:
>
> changing CONFIG_LOG_BUF_SHIFT=18 to CONFIG_LOG_BUF_SHIFT=20 helps, but
> nevertheless:

FWIW, you can also use the boot argument "log_buf_len" to dynamically
allocate the dmesg buffer at boot.

For example: log_buf_len=16M

This is usually more convenient than reconfiguring/rebuilding your
kernel.

John Ogness