diff options
author | Daniel Borkmann <dborkman@redhat.com> | 2014-08-26 23:16:35 -0400 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2014-10-17 11:37:29 -0400 |
commit | d4c5efdb97773f59a2b711754ca0953f24516739 (patch) | |
tree | 83ededeb92d6d529e8081b97b2f9cdf491094b78 /block/blk-cgroup.h | |
parent | 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9 (diff) | |
download | linux-stable-d4c5efdb97773f59a2b711754ca0953f24516739.tar.gz linux-stable-d4c5efdb97773f59a2b711754ca0953f24516739.tar.bz2 linux-stable-d4c5efdb97773f59a2b711754ca0953f24516739.zip |
random: add and use memzero_explicit() for clearing data
zatimend has reported that in his environment (3.16/gcc4.8.3/corei7)
memset() calls which clear out sensitive data in extract_{buf,entropy,
entropy_user}() in random driver are being optimized away by gcc.
Add a helper memzero_explicit() (similarly as explicit_bzero() variants)
that can be used in such cases where a variable with sensitive data is
being cleared out in the end. Other use cases might also be in crypto
code. [ I have put this into lib/string.c though, as it's always built-in
and doesn't need any dependencies then. ]
Fixes kernel bugzilla: 82041
Reported-by: zatimend@hotmail.co.uk
Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@vger.kernel.org
Diffstat (limited to 'block/blk-cgroup.h')
0 files changed, 0 insertions, 0 deletions