Red Hat Bugzilla – Bug 481683
kmod-cmirror package modules causing tainted kernel error on RHEL5.3
Last modified: 2009-01-26 21:47:46 EST
Description of problem:
A package that ships with RHEL5.3 causes a tainted kernel. From the output of the hardware test suite (hts-5.2-20) INFO test, I believe the file causing the problem is dm-log-clustered.ko, which is part of the kmod-cmirror package(s):
OS Version: Red Hat Enterprise Linux Server release 5.3 (Tikanga)
Kernel RPM: kernel-xen-2.6.18-128.el5
HTS version 5.2, release 20
+ rpm -ql kernel-xen-2.6.18-128.el5
Error: kernel is tainted (value = 64)
Boot Parameters: ro root=LABEL=/1 rhgb quiet
Error: Kernel check failed.
HTS Verify passed
Non-Red Hat kernel module dm_log_clustered
Red Hat Enterprise Linux RHEL5 ABI
Error: The following symbols are used by dm_log_clustered are not on the ABI whitelist.
Strangely enough, these modules pass the online verification at http://www.kerneldrivers.org/abi_check.php. Does that site use an updated version of the kabi_whitelist file? The local python version of the test which reads from the local kabi_whitelist file fails with the same output as the INFO test (which may incorporate the exact same script).
This error causes a problem for hardware certification, which checks for tainted kernels and fails a required test if /proc/sys/kernel/tainted is a non-zero value. This will also cause problems for our support staff, when anyone with Cluster Storage packages installed has sosreports that report tainted kernels.
Version-Release number of selected component (if applicable):
RHEL5.3 2.6.18-128 xen and bare metal kernel with the modules from
Steps to Reproduce:
1. Install RHEL 5.3 with Clustering and Cluster Storage package groups
2. Check contents of /proc/sys/kernel/tainted
3. Value is 64 (non-zero)
Also can simply insmod dm-log-clustered.ko for same kernel taint value.
Tainted kernel report.
Non-tainted kernel when using only Red Hat provided software.
I'm closing this ticket and opening two separate ones instead. The issue is actually two different problems. The kabi_whitelist issue is not what causes the tainted kernel error, it's a lack of signed modules.