The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, mpm@selenic.com, akpm@linux-foundation.org
Subject: Re: [PATCH] random: add a way to get some random bits into the entropy pools early on
Date: Wed, 26 Nov 2008 15:02:02 +0100	[thread overview]
Message-ID: <878wr6d1r9.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20081125132600.5112fb24@infradead.org> (Arjan van de Ven's message of "Tue, 25 Nov 2008 13:26:00 -0800")

Arjan van de Ven <arjan@infradead.org> writes:

> From 5b3b09ac82316c2d4000460d586ebe59303c12c2 Mon Sep 17 00:00:00 2001
> From: Arjan van de Ven <arjan@linux.intel.com>
> Date: Tue, 25 Nov 2008 11:41:37 -0800
> Subject: [PATCH] random: add a way to get some random bits into the entropy pools early on
>
> currently the entropy pool gets seeded on the module_init() level, but there
> is at least one consumer of random bits (the oops ID that is printed as part
> of the oops).
> As a result of this, kerneloops.org is seeing a lot of oopses that all share
> the same 'random' number; which used to get filed away as "duplicate".

This should also help networking, which also relies on some non existant
randomness early on currently.

But I think i would prefer to move the complete random initialization
earlier instead of having special case calls for this.

Feeding in DMI and some other system data and perhaps
some other register values would be also a good idea.
The utsname initialization that is currently in there I always found
amusing because there is no way utsname is set that early.

-Andi

-- 
ak@linux.intel.com

      parent reply	other threads:[~2008-11-26 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 21:26 [PATCH] random: add a way to get some random bits into the entropy pools early on Arjan van de Ven
2008-11-25 21:41 ` Matt Mackall
2008-11-26  6:06   ` Arjan van de Ven
2008-11-26  1:09 ` Andrew Morton
2008-11-26  2:51 ` Ingo Molnar
2008-11-26 14:02 ` Andi Kleen [this message]

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=878wr6d1r9.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    /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