Revision 9f28ffc03e93343ac04874fda9edb7affea45165 authored by David S. Miller on 19 December 2012, 23:19:11 UTC, committed by David S. Miller on 19 December 2012, 23:19:11 UTC
The basic scheme of the block mode assembler is that we start by enabling the FPU, loading the key into the floating point registers, then iterate calling the encrypt/decrypt routine for each block. For the 256-bit key cases, we run short on registers in the unrolled loops. So the {ENCRYPT,DECRYPT}_256_2() macros reload the key registers that get clobbered. The unrolled macros, {ENCRYPT,DECRYPT}_256(), are not mindful of this. So if we have a mix of multi-block and single-block calls, the single-block unrolled 256-bit encrypt/decrypt can run with some of the key registers clobbered. Handle this by always explicitly loading those registers before using the non-unrolled 256-bit macro. This was discovered thanks to all of the new test cases added by Jussi Kivilinna. Signed-off-by: David S. Miller <davem@davemloft.net>
1 parent 4a9d194
File | Mode | Size |
---|---|---|
governors | ||
Kconfig | -rw-r--r-- | 1.0 KB |
Makefile | -rw-r--r-- | 195 bytes |
coupled.c | -rw-r--r-- | 23.4 KB |
cpuidle-calxeda.c | -rw-r--r-- | 3.8 KB |
cpuidle.c | -rw-r--r-- | 11.8 KB |
cpuidle.h | -rw-r--r-- | 1.9 KB |
driver.c | -rw-r--r-- | 5.6 KB |
governor.c | -rw-r--r-- | 3.2 KB |
sysfs.c | -rw-r--r-- | 15.2 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...