From: "Theodore Ts'o" <tytso@mit.edu>
To: "Dilger, Andreas" <andreas.dilger@intel.com>
Cc: Greg KH <greg@kroah.com>, Peng Tao <tao.peng@emc.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: lustre: why does cfs_get_random_bytes() exist?
Date: Thu, 3 Oct 2013 19:45:45 -0400 [thread overview]
Message-ID: <20131003234545.GA19796@thunk.org> (raw)
In-Reply-To: <CE732F62.74A88%andreas.dilger@intel.com>
On Thu, Oct 03, 2013 at 11:06:58PM +0000, Dilger, Andreas wrote:
>
> The Lustre cfs_get_random_bytes() incorporates (via cfs_rand()) a seed
> which
> also hashes in the addresses from any network interfaces that are
> configured.
> Conversely, cfs_rand() also is seeded at startup from get_random_bytes() in
> case a hardware RNG is available. This ensures even with identical initial
> conditions cfs_get_random_bytes() gets a different random stream on each
> node.
With modern kernels, the /dev/random driver has the
add_device_randomness() interface which is used to mix in
personalization information, which includes the network MAC address.
So that particular concern should be covered without the hack of
mixing in cfs_rand().
> I'm not against cleaning this up, if there is some mechanism for the
> startup code to add in the node interface addresses into the entropy
> pool, and this is also used to perturb the prandom_u32() sequence
> after that point.
That's handled too, via the late initcall prandom_reseed().
Cheers,
- Ted
next prev parent reply other threads:[~2013-10-03 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 16:39 lustre: why does cfs_get_random_bytes() exist? Theodore Ts'o
2013-10-03 17:26 ` Greg KH
2013-10-03 19:34 ` Theodore Ts'o
2013-10-03 23:06 ` Dilger, Andreas
2013-10-03 23:45 ` Theodore Ts'o [this message]
2013-10-05 6:10 ` Dilger, Andreas
2013-10-05 14:21 ` Theodore Ts'o
2013-10-05 15:51 ` Christoph Hellwig
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=20131003234545.GA19796@thunk.org \
--to=tytso@mit.edu \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tao.peng@emc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.