Red Hat Bugzilla – Bug 438288
aes module in 2.6.18-84.el5 depends on padlock.ko
Last modified: 2008-06-19 10:29:44 EDT
Description of problem:
In RHEL 5.2 beta, kernel version 2.6.18-84.el5. When ever i try to load
the aes module, it tries to load the padlock.ko module and fails.
The aes module seems to have been replaced by aes_generic in 5.2 is this a bug?
Version-Release number of selected component (if applicable):
[root@huzaifas ~]# uname -r
[root@huzaifas ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Client release 5.2 Beta (Tikanga)
[root@huzaifas ~]# modprobe aes
WARNING: Error inserting padlock
(/lib/modules/2.6.18-84.el5/kernel/drivers/crypto/padlock.ko): No such device
[root@huzaifas ~]# lsmod | grep aes
aes_generic 31745 0
aes_i586 37057 1
I guess aes module is replaced aes_generic in 5.2 and aes now implies the
padlock dep. module.
This should be put in the release notes.
If i wasnt clear on my above comments then:
aes = arch independent
aes = dep on padlock
aes_generic = arch independent
AFAICT, aes_generic does not require the padlock module -- furthermore, the
padlock module is not built in RHEL5.
Closing as WORKSFORME. Huzaifa, please re-open this BZ if this still doesn't
work for you.
It doesn't require padlock, but padlock is one of the modules that provide the
alias aes. Therefore if you load aes on a kernel with padlock built as a module
it will attempt to load the padlock module as well as all other AES
implementations. Failing to load the padlock module when padlock is not
available is expected and not an error.
*** Bug 437272 has been marked as a duplicate of this bug. ***