[v1] random: re-add removed comment about get_random_{u32,u64} reseeding

[PATCH] random: re-add removed comment about get_random_{u32,u64} reseeding

Jason A. Donenfeld posted 1 patch 4 years, 3 months ago

Diff against v2
Download mbox

There is a newer version of this series

drivers/char/random.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Expand all Fold all

[PATCH] random: re-add removed comment about get_random_{u32,u64} reseeding

Posted by Jason A. Donenfeld 4 years, 3 months ago

The comment about get_random_{u32,u64}() not invoking reseeding got
added in an unrelated commit, that then was recently reverted. So this
adds that little comment snippet back.

Cc: Dominik Brodowski <linux@dominikbrodowski.net>
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
---
 drivers/char/random.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/char/random.c b/drivers/char/random.c
index 1d7aac2a9600..82e37d7dd9f1 100644
--- a/drivers/char/random.c
+++ b/drivers/char/random.c
@@ -226,7 +226,7 @@ static void _warn_unseeded_randomness(const char *func_name, void *caller, void
  * into the given buffer or as a return value. This is equivalent to
  * a read from /dev/urandom. The integer family of functions may be
  * higher performance for one-off random integers, because they do a
- * bit of buffering.
+ * bit of buffering and do not invoke reseeding.
  *
  *********************************************************************/
 
-- 
2.35.1