From: Oliver Xymoron <oxymoron@waste.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/7] /dev/random cleanup
Date: Sat, 28 Sep 2002 00:50:40 -0500 [thread overview]
Message-ID: <20020928055040.GM21969@waste.org> (raw)
[resent with current l-k address]
Linus,
The following patches against 2.5.39 clean up the RNG support
substantially. Please pay special attention to the first patch, which
fixes two major bugs in the reseeding logic. They can be easily
demonstrated by running 'cat /dev/random | hexdump' on a quiescent
system. When it blocks, lightly tapping the mouse generates a large
stream of additional output, despite very little entropy being added.
The second and third patches introduce my fixes for the more
theoretical issues and should address all the issues that have been
raised.
The fourth and fifth make the pool and reseeding logic much more clear
and create a new pool for /dev/urandom that avoids starving
/dev/random readers.
Six and seven propagate the new API to the rest of the kernel and
remove dead code.
Please apply.
--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."
reply other threads:[~2002-09-28 5:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020928055040.GM21969@waste.org \
--to=oxymoron@waste.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).