From: Greg Price <price@MIT.EDU>
Date: Fri, 29 Nov 2013 19:59:45 +0000 (-0500)
Subject: random: fix description of get_random_bytes
X-Git-Tag: firefly_0821_release~176^2~4142^2~13
X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=18e9cea74951b64282964f9625db94c5d5a007bd;p=firefly-linux-kernel-4.4.55.git

random: fix description of get_random_bytes

After this remark was written, commit d2e7c96af added a use of
arch_get_random_long() inside the get_random_bytes codepath.
The main point stands, but it needs to be reworded.

Signed-off-by: Greg Price <price@mit.edu>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
---

diff --git a/drivers/char/random.c b/drivers/char/random.c
index f0eea5fdc1b7..fcda7d3937e0 100644
--- a/drivers/char/random.c
+++ b/drivers/char/random.c
@@ -1170,8 +1170,9 @@ static ssize_t extract_entropy_user(struct entropy_store *r, void __user *buf,
 /*
  * This function is the exported kernel interface.  It returns some
  * number of good random numbers, suitable for key generation, seeding
- * TCP sequence numbers, etc.  It does not use the hw random number
- * generator, if available; use get_random_bytes_arch() for that.
+ * TCP sequence numbers, etc.  It does not rely on the hardware random
+ * number generator.  For random bytes direct from the hardware RNG
+ * (when available), use get_random_bytes_arch().
  */
 void get_random_bytes(void *buf, int nbytes)
 {