[PATCH 00/10] /dev/random fixups

From: Theodore Ts'o
Date: Thu Jul 05 2012 - 14:13:57 EST


This patch series addresses some shortcomings in the /dev/random driver
discovered by Zakir Durumeric, Nadia Halderman, J. Alex Heninger, and
Eric Wustrow. For more information please see https://factorable.net/

One notable change from previous versions of this patch is that I'm now
fixing in the EIP from the interrupt handler into entropy pool as well
as the timestamp, in order to add more variability. In addition, if the
CPU has a hardware random number generator, we use it in
xfer_secondary_pool so that some input from the CPU's HWRNG is mixed in
whenever we generate random bytes.

Thanks to Dan Carbenter, Thomas Gleixner, Greg K-H, David Miller, Willy
Tarreau, Linus Torvalds, and Eric Wustrow who all provided very valuable
input, testing, and code.

Please review and comment; the plan is for Linus to pull them during the
next merge window.

- Ted

Linus Torvalds (1):
random: create add_device_randomness() interface

Theodore Ts'o (9):
random: make 'add_interrupt_randomness()' do something sane
random: use lockless techniques when mixing entropy pools
usb: feed USB device information to the /dev/random driver
net: feed /dev/random with the MAC address when registering a device
random: use the arch-specific rng in xfer_secondary_pool
random: add new get_random_bytes_arch() function
random: unify mix_pool_bytes() and mix_pool_bytes_entropy()
random: add tracepoints for easier debugging and verification
MAINTAINERS: Theodore Ts'o is taking over the random driver

MAINTAINERS | 4 +-
drivers/char/random.c | 223 ++++++++++++++++++++++++++++++++----------
drivers/mfd/ab3100-core.c | 2 -
drivers/usb/core/hub.c | 9 ++
include/linux/random.h | 2 +
include/trace/events/random.h | 132 +++++++++++++++++++++++++
kernel/irq/handle.c | 3 +-
net/core/dev.c | 3 +
8 files changed, 319 insertions(+), 59 deletions(-)
create mode 100644 include/trace/events/random.h

--
1.7.11.1.108.gb129051

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/