Use crypto_alloc_base() instead of crypto_alloc_ablkcipher() to
allocate underlying tfm in cryptd_alloc_ablkcipher. Because
crypto_alloc_ablkcipher() prefer GENIV encapsulated crypto instead of
raw one, while cryptd_alloc_ablkcipher needed the raw one.
Signed-off-by: Huang Ying
---
crypto/crypt
Blkcipher touching FPU need to be enclosed by kernel_fpu_begin() and
kernel_fpu_end(). If they are invoked in cipher algorithm
implementation, they will be invoked for each block, so that
performance will be hurt, because they are "slow" operations. This
patch implements "fpu" template, which makes
Because kernel_fpu_begin() and kernel_fpu_end() operations are too
slow, the performance gain of general mode implementation + aes-aesni
is almost all compensated.
The AES-NI support for more modes are implemented as follow:
- Add a new AES algorithm implementation named __aes-aesni without
ker
On Sat, 7 Mar 2009, Melchior FRANZ wrote:
> I was about to report an oops in the crypt module (NULL pointer
> dereferencing), but when I was half-way through entering the bug
> in bugzilla, I read that people with nvidia tainted kernels aren't
> supposed to file bug reports.
>
> So the bug is goin
Melchior FRANZ wrote:
> I was about to report an oops in the crypt module (NULL pointer
> dereferencing), but when I was half-way through entering the bug
> in bugzilla, I read that people with nvidia tainted kernels aren't
> supposed to file bug reports.
>
> So the bug is going to remain unfixed!
