mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 5.18.1 has thousands of similar lines in dmesg with CONFIG_WARN_ALL_UNSEEDED_RANDOM=y
Date: Mon, 30 May 2022 21:47:01 +0200	[thread overview]
Message-ID: <YpUfNc9XcdA5KqJ4@zx2c4.com> (raw)
In-Reply-To: <83b4b916-1334-e3b0-cb1e-6cd12ae0ddff@gmx.de>

Hi Toralf,

On Mon, May 30, 2022 at 11:24:55AM +0200, Toralf Förster wrote:
> This deletes the early boot messages in dmesg:
> 
> /var/log # head dmesg
> [    3.114274] random: get_random_u32 called from
> allocate_slab+0x144/0x480 with crng_init=0
> [    3.114286] random: get_random_u32 called from
> allocate_slab+0x144/0x480 with crng_init=0
> [    3.114291] random: get_random_u32 called from
> allocate_slab+0x144/0x480 with crng_init=0
> [    3.114297] random: get_random_u32 called from
> allocate_slab+0x144/0x480 with crng_init=0
> [    3.114304] random: get_random_u32 called from
> allocate_slab+0x144/0x480 with crng_init=0
> [    3.114315] random: get_random_u32 called from
> allocate_slab+0x144/0x480 with crng_init=0
> [    3.114323] random: get_random_u32 called from
> allocate_slab+0x144/0x480 with crng_init=0
> [    3.114329] random: get_random_u32 called from
> allocate_slab+0x144/0x480 with crng_init=0
> [    3.114333] random: get_random_u32 called from
> allocate_slab+0x144/0x480 with crng_init=0
> [    3.114345] random: get_random_u32 called from
> allocate_slab+0x144/0x480 with crng_init=0

This was simplified here:

    https://lore.kernel.org/lkml/20220509172426.612649-1-Jason@zx2c4.com/
    https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cc1e127bfa95b5fb2f9307e7168bf8b2b45b4c5e

I'm happy to consider other heuristics than the one there if you find
this one problematic. But I think as a debug option, the current
behavior encapsulates well what somebody might want to know when
debugging a kernel. Either way, please let me know if this poses a
problem for you.

Jason

  parent reply	other threads:[~2022-05-30 19:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30  9:24 Toralf Förster
2022-05-30 13:49 ` Toralf Förster
2022-05-30 19:52   ` John Ogness
2022-05-30 19:59     ` Toralf Förster
2022-05-30 19:47 ` Jason A. Donenfeld [this message]
2022-05-30 19:59   ` Toralf Förster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YpUfNc9XcdA5KqJ4@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toralf.foerster@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®