Hi Stephan,
I checked modinfo aesni_intel:
filename: /lib/modules/4.5.0/kernel/arch/x86/crypto/aesni-intel.ko
alias: crypto-aes
alias: aes
license: GPL
description: Rijndael (AES) Cipher Algorithm, Intel AES-NI
instructions optimized
alias: crypto-fpu
alias: fpu
srcversion: 55C6346DCF663DDD74D3F13
alias: cpu:type:x86,ven*fam*mod*:feature:*0099*
depends: xts,aes-i586,lrw,ablk_helper
intree: Y
vermagic: 4.5.0 SMP mod_unload modversions 686
when I do modprobe crypto-aes,
modprobe: ERROR: could not insert 'aesni_intel': No such device
modprobe: ERROR: could not insert 'padlock_aes': No such device
I have these modules: xts,aes-i586,lrw,ablk_helper loaded as well (
the dependencies).
I think I am still missing something. Any hardware feature. Or some
other module is using some IRQ or region which is not shared.
Thanks.
Nayan Gadre.
On Mon, May 2, 2016 at 11:21 AM, Stephan Mueller <smueller@xxxxxxxxxx> wrote:
> Am Montag, 2. Mai 2016, 11:14:01 schrieb Gadre Nayan:
>
> Hi Gadre,
>
>> Hello,
>>
>> I have read the crypto library documentation on chronox.de.
>>
>> I used there sample code for symmetric key cipher operation.
>> However in the check:
>>
>> skcipher = crypto_alloc_skcipher("cbc-aes-aesni", 0, 0);
>> if (IS_ERR(skcipher)) {
>> pr_info("could not allocate skcipher handle\n");
>> return PTR_ERR(skcipher);
>> }
>>
>> I get could not allocate skcipher handle.
>>
>> I have loaded all possible related modules for crypto:
>> lsmod (relevant):
>> algif_skcipher 32768 0
>> algif_hash 20480 0
>> algif_aead 20480 0
>> af_alg 24576 3 algif_aead,algif_hash,algif_skcipher
>> cryptd
>> ablk_helper.
>>
>> What am I missing here?
>>
>> Also IS_ERR checks if the skcipher value may be <1000, it may include
>> the NULL check right?.
>
> The allocation of the cipher failed. Please check /proc/crypto whether you
> have the cipher registered with the kernel crypto API.
>
> The module listing does not show the AESNI cipher module.
>
> Ciao
> Stephan
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
