The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] random: add a way to get some random bits into the entropy pools early on
Date: Tue, 25 Nov 2008 15:41:22 -0600	[thread overview]
Message-ID: <1227649282.3196.3.camel@calx> (raw)
In-Reply-To: <20081125132600.5112fb24@infradead.org>

On Tue, 2008-11-25 at 13:26 -0800, Arjan van de Ven wrote:
> >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 patch adds a function to the random driver so that various pieces of
> the kernel can add random bits (but not entropy!) to the pool, to avoid
> this dupicate ID problem.

This appears to be equivalent to making random initialize earlier,
except with more code?

If we're going down a route like this, I'd like to see the ability to
actually mix in data (ie MAC addresses, DMI data, etc.) rather than just
timing.

-- 
Mathematics is the supreme nostalgia of our time.


  reply	other threads:[~2008-11-26  4:01 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 [this message]
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

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=1227649282.3196.3.camel@calx \
    --to=mpm@selenic.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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