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 | a5e9f557098e54af44ade5d501379be18435bfbf (patch) | |
tree | 4410647aaa269fd9a4e304851b06f83251b12853 /mm/percpu-vm.c | |
parent | 78105c7e769b8cfa4a4d59027807882b560a2634 (diff) | |
download | linux-a5e9f557098e54af44ade5d501379be18435bfbf.tar.gz linux-a5e9f557098e54af44ade5d501379be18435bfbf.tar.bz2 linux-a5e9f557098e54af44ade5d501379be18435bfbf.zip |
crypto: chacha20 - Fix chacha20_block() keystream alignment (again)
In commit 9f480faec58c ("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 'mm/percpu-vm.c')
0 files changed, 0 insertions, 0 deletions