From: "H. Peter Anvin" <hpa@linux.intel.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DJ Johnston <dj.johnston@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"H. Peter Anvin" <hpa@linux.intel.com>
Subject: [PATCH v2 0/2] random: Account for entropy loss due to overwrites
Date: Tue, 20 Nov 2012 23:27:46 -0800 [thread overview]
Message-ID: <1353482868-8064-1-git-send-email-hpa@linux.intel.com> (raw)
From: "H. Peter Anvin" <hpa@linux.intel.com>
When we write entropy into a non-empty pool, we currently don't
account at all for the fact that we will probabilistically overwrite
some of the entropy in that pool. This means that unless the pool is
fully empty, we are currently *guaranteed* to overestimate the amount
of entropy in the pool!
This version of the patchset avoids manually duplicating information
by using a macro. This removes *all* dynamic computation of derived
pool information and replaces them with static information: on just
about every architecture accessing pointer+offset is no more expensive
than just plain pointer, and this lets us get the information we
actually need from the start.
next reply other threads:[~2012-11-21 7:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 7:27 H. Peter Anvin [this message]
2012-11-21 7:27 ` [PATCH v2 1/2] random: Statically compute poolbitshift, poolbytes, poolbits H. Peter Anvin
2012-11-21 7:27 ` [PATCH v2 2/2] random: Account for entropy loss due to overwrites H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2013-04-24 4:26 [PATCH v2 0/2] " H. Peter Anvin
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=1353482868-8064-1-git-send-email-hpa@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=dj.johnston@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.