diff options
author | Eric Biggers <ebiggers@google.com> | 2018-09-11 20:05:10 -0700 |
---|---|---|
committer | Herbert Xu <herbert@gondor.apana.org.au> | 2018-09-21 13:24:50 +0800 |
commit | 7a55a1c19d1ccff6d76aab3b07016f112754c19b (patch) | |
tree | 1bc054a511a56dfde52f759a0fd307e03cc913bd /crypto/ecc.h | |
parent | e75189cd49c69fc564c4b815b30e2ac9867809e5 (diff) | |
download | linux-crypto-7a55a1c19d1ccff6d76aab3b07016f112754c19b.tar.gz linux-crypto-7a55a1c19d1ccff6d76aab3b07016f112754c19b.zip |
crypto: chacha20 - Fix chacha20_block() keystream alignment (again)
In commit 49b79ef83e36 ("crypto: chacha20 - Fix keystream alignment for
chacha20_block()"), I had missed that chacha20_block() can be called
directly on the buffer passed to get_random_bytes(), which can have any
alignment. So, while my commit didn't break anything, it didn't fully
solve the alignment problems.
Revert my solution and just update chacha20_block() to use
put_unaligned_le32(), so the output buffer need not be aligned.
This is simpler, and on many CPUs it's the same speed.
But, I kept the 'tmp' buffers in extract_crng_user() and
_get_random_bytes() 4-byte aligned, since that alignment is actually
needed for _crng_backtrack_protect() too.
Reported-by: Stephan Müller <smueller@chronox.de>
Cc: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'crypto/ecc.h')
0 files changed, 0 insertions, 0 deletions