Note that by itself, having a "hardware" random generator does very little: you should probably run "rngd" in your guest to feed this into the kernel entropy pool. Included: virtio_rng: dont use vmalloced addresses for virtio If virtio_rng is build as a module, random_data is an address in vmalloc space. As virtio expects guest real addresses, this can cause any kind of funny behaviour, so lets allocate random_data dynamically with kmalloc. Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> |
||
---|---|---|
.. | ||
Kconfig | ||
Makefile | ||
amd-rng.c | ||
core.c | ||
geode-rng.c | ||
intel-rng.c | ||
ixp4xx-rng.c | ||
omap-rng.c | ||
pasemi-rng.c | ||
via-rng.c | ||
virtio-rng.c |