summaryrefslogtreecommitdiffstats
path: root/crypto/aes_generic.c
diff options
context:
space:
mode:
authorCesar Eduardo Barros <cesarb@cesarb.eti.br>2013-11-26 01:00:41 +0100
committerHerbert Xu <herbert@gondor.apana.org.au>2013-12-05 14:28:41 +0100
commitfe8c8a126806fea4465c43d62a1f9d273a572bf5 (patch)
treeea40ae4afce934575065383d1de44d04cd6490fc /crypto/aes_generic.c
parentcrypto: talitos - fix locating offending descriptor in error path (diff)
downloadlinux-fe8c8a126806fea4465c43d62a1f9d273a572bf5.tar.xz
linux-fe8c8a126806fea4465c43d62a1f9d273a572bf5.zip
crypto: more robust crypto_memneq
Disabling compiler optimizations can be fragile, since a new optimization could be added to -O0 or -Os that breaks the assumptions the code is making. Instead of disabling compiler optimizations, use a dummy inline assembly (based on RELOC_HIDE) to block the problematic kinds of optimization, while still allowing other optimizations to be applied to the code. The dummy inline assembly is added after every OR, and has the accumulator variable as its input and output. The compiler is forced to assume that the dummy inline assembly could both depend on the accumulator variable and change the accumulator variable, so it is forced to compute the value correctly before the inline assembly, and cannot assume anything about its value after the inline assembly. This change should be enough to make crypto_memneq work correctly (with data-independent timing) even if it is inlined at its call sites. That can be done later in a followup patch. Compile-tested on x86_64. Signed-off-by: Cesar Eduardo Barros <cesarb@cesarb.eti.br> Acked-by: Daniel Borkmann <dborkman@redhat.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'crypto/aes_generic.c')
0 files changed, 0 insertions, 0 deletions