Bug 438288 - aes module in 2.6.18-84.el5 depends on padlock.ko
Summary: aes module in 2.6.18-84.el5 depends on padlock.ko
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.2
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Martin Jenner
: 437272 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2008-03-20 07:36 UTC by Huzaifa S. Sidhpurwala
Modified: 2008-06-19 14:29 UTC (History)
4 users (show)

Clone Of:
Last Closed: 2008-05-12 17:58:45 UTC

Attachments (Terms of Use)

Description Huzaifa S. Sidhpurwala 2008-03-20 07:36:54 UTC
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)

How reproducible:
[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

Comment 1 Huzaifa S. Sidhpurwala 2008-03-20 09:08:53 UTC
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.

Comment 2 Huzaifa S. Sidhpurwala 2008-03-20 09:10:01 UTC
If i wasnt clear on my above comments then:

RHEL 5/5.1
aes = arch independent

RHEL 5.2
aes = dep on padlock
aes_generic = arch independent

Comment 3 Prarit Bhargava 2008-05-12 17:58:45 UTC

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.


Comment 4 Herbert Xu 2008-05-13 02:54:28 UTC
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.

Comment 5 Milan Broz 2008-06-19 14:29:02 UTC
*** Bug 437272 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.