4.10 aesni-intel no longer having lrw/ablk_helper dependencies?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi.

[arekm@xps ~]$ modinfo --set-version 4.9.6 aesni-intel | grep depends
depends:        glue_helper,aes-x86_64,lrw,cryptd,ablk_helper

[arekm@xps ~]$ modinfo --set-version  4.10.0-rc5-00161-gfd694aaa46c7 aesni-
intel |grep depends
depends:        glue_helper,aes-x86_64,crypto_simd,cryptd

With 4.10.0 lrw and ablk_helper are no longer in dependencies while
aesni-intel seem to still need these. My luks encrypted rootfs fails to 
unlock. Initrd generation script only installs modules based on dependencies 
and that seems to be a reason for luks unlock failure with 4.10rc - some 
missing modules.

Failure looks like that:
$ insmod path/to/aesni-intel.ko
dmesg gets logged:
"AVX2 version of gcm_enc/dec engaged
AES CTR mode by8 optimization enabled."
and insmod reports that it cannot insert aesni-intel because of unresolved 
symbol or unknown option but nothing more is logged in dmesg.

4.9.x works fine.

What did change/how to figure out deps now?

Both modules exist:
[arekm@xps ~]$ modinfo --set-version  4.10.0-rc5-00161-gfd694aaa46c7 lrw
filename:       /lib/modules/4.10.0-rc5-00161-
gfd694aaa46c7/kernel/crypto/lrw.ko.xz
alias:          crypto-lrw
alias:          lrw
description:    LRW block cipher mode
license:        GPL
depends:        gf128mul
intree:         Y
vermagic:       4.10.0-rc5-00161-gfd694aaa46c7 SMP preempt mod_unload
signat:         PKCS#7
signer:
sig_key:
sig_hashalgo:   md4

[arekm@xps ~]$ modinfo --set-version  4.10.0-rc5-00161-gfd694aaa46c7 
ablk_helper
filename:       /lib/modules/4.10.0-rc5-00161-
gfd694aaa46c7/kernel/crypto/ablk_helper.ko.xz
license:        GPL
depends:        cryptd
intree:         Y
vermagic:       4.10.0-rc5-00161-gfd694aaa46c7 SMP preempt mod_unload
signat:         PKCS#7
signer:
sig_key:
sig_hashalgo:   md4


-- 
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
--
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




[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux