aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJason A. Donenfeld <Jason@zx2c4.com>2018-02-04 17:07:46 -0500
committerTheodore Ts'o <tytso@mit.edu>2018-02-28 17:59:21 -0500
commit25e3fca492035a2e1d4ac6e3b1edd9c1acd48897 (patch)
tree18b2960df3683d779c53b8f591463091eae30f19
parent9f886f4d1d292442b2f22a0a33321eae821bde40 (diff)
random: always fill buffer in get_random_bytes_wait
In the unfortunate event that a developer fails to check the return value of get_random_bytes_wait, or simply wants to make a "best effort" attempt, for whatever that's worth, it's much better to still fill the buffer with _something_ rather than catastrophically failing in the case of an interruption. This is both a defense in depth measure against inevitable programming bugs, as well as a means of making the API a bit more useful. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
-rw-r--r--include/linux/random.h4
1 files changed, 1 insertions, 3 deletions
diff --git a/include/linux/random.h b/include/linux/random.h
index 4024f7d9c77d..2ddf13b4281e 100644
--- a/include/linux/random.h
+++ b/include/linux/random.h
@@ -85,10 +85,8 @@ static inline unsigned long get_random_canary(void)
85static inline int get_random_bytes_wait(void *buf, int nbytes) 85static inline int get_random_bytes_wait(void *buf, int nbytes)
86{ 86{
87 int ret = wait_for_random_bytes(); 87 int ret = wait_for_random_bytes();
88 if (unlikely(ret))
89 return ret;
90 get_random_bytes(buf, nbytes); 88 get_random_bytes(buf, nbytes);
91 return 0; 89 return ret;
92} 90}
93 91
94#define declare_get_random_var_wait(var) \ 92#define declare_get_random_var_wait(var) \