diff options
author | Daniel Borkmann <dborkman@redhat.com> | 2014-08-26 23:16:35 -0400 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-11-14 08:47:55 -0800 |
commit | 25e1465ac3cfeafce34b3a47e773c4bc950054a3 (patch) | |
tree | 31d1c7845bb872d25967f82d253b31b0561bdc1c /include/scsi | |
parent | 620c41147d873223d8aac0aa64793882b6217f09 (diff) | |
download | lwn-25e1465ac3cfeafce34b3a47e773c4bc950054a3.tar.gz lwn-25e1465ac3cfeafce34b3a47e773c4bc950054a3.zip |
random: add and use memzero_explicit() for clearing data
commit d4c5efdb97773f59a2b711754ca0953f24516739 upstream.
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include/scsi')
0 files changed, 0 insertions, 0 deletions