diff options
| author | Arvind Sankar <nivedita@alum.mit.edu> | 2020-10-25 10:31:14 -0400 |
|---|---|---|
| committer | Herbert Xu <herbert@gondor.apana.org.au> | 2020-10-30 17:35:03 +1100 |
| commit | 1762818f25f3f99c5083caa13d69e5e5aa2e4b6f (patch) | |
| tree | 09fd538f8085ed4d5f944eaa50eaabb6177fa9e9 /usr | |
| parent | 383e8a823014532ffd81c787ef9009f1c2bd3b79 (diff) | |
| download | linux-1762818f25f3f99c5083caa13d69e5e5aa2e4b6f.tar.gz linux-1762818f25f3f99c5083caa13d69e5e5aa2e4b6f.tar.bz2 linux-1762818f25f3f99c5083caa13d69e5e5aa2e4b6f.zip | |
crypto: lib/sha256 - Use memzero_explicit() for clearing state
Without the barrier_data() inside memzero_explicit(), the compiler may
optimize away the state-clearing if it can tell that the state is not
used afterwards. At least in lib/crypto/sha256.c:__sha256_final(), the
function can get inlined into sha256(), in which case the memset is
optimized away.
Signed-off-by: Arvind Sankar <nivedita@alum.mit.edu>
Reviewed-by: Eric Biggers <ebiggers@google.com>
Acked-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'usr')
0 files changed, 0 insertions, 0 deletions