summaryrefslogtreecommitdiffstats
path: root/mm/hugetlb.c
diff options
context:
space:
mode:
authorJarod Wilson <jarod@redhat.com>2011-02-21 11:43:10 +0100
committerHerbert Xu <herbert@gondor.apana.org.au>2011-02-21 12:42:42 +0100
commit442a4fffffa26fc3080350b4d50172f7589c3ac2 (patch)
tree18f99b2ab50cda90bc64ad49560860729a92c1c2 /mm/hugetlb.c
parentcrypto: picoxcell - add support for the picoxcell crypto engines (diff)
downloadlinux-442a4fffffa26fc3080350b4d50172f7589c3ac2.tar.xz
linux-442a4fffffa26fc3080350b4d50172f7589c3ac2.zip
random: update interface comments to reflect reality
At present, the comment header in random.c makes no mention of add_disk_randomness, and instead, suggests that disk activity adds to the random pool by way of add_interrupt_randomness, which appears to not have been the case since sometime prior to the existence of git, and even prior to bitkeeper. Didn't look any further back. At least, as far as I can tell, there are no storage drivers setting IRQF_SAMPLE_RANDOM, which is a requirement for add_interrupt_randomness to trigger, so the only way for a disk to contribute entropy is by way of add_disk_randomness. Update comments accordingly, complete with special mention about solid state drives being a crappy source of entropy (see e2e1a148bc for reference). Signed-off-by: Jarod Wilson <jarod@redhat.com> Acked-by: Matt Mackall <mpm@selenic.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'mm/hugetlb.c')
0 files changed, 0 insertions, 0 deletions