Bug 481683

Summary:	kmod-cmirror package modules causing tainted kernel error on RHEL5.3
Product:	Red Hat Enterprise Linux 5	Reporter:	Gary Case <gcase>
Component:	kernel	Assignee:	Red Hat Kernel Manager <kernel-mgr>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Mike Gahagan <mgahagan>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.3
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-01-27 02:47:46 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gary Case 2009-01-27 01:37:54 UTC

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):

Running ./info.py:
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
--------------------------------

Module: dm_log_clustered
Kernel: 2.6.18-128.el5xen
Whitelist: /usr/src/kernels/2.6.18-128.el5xen-x86_64/kabi_whitelist

Error: The following symbols are used by dm_log_clustered are not on the ABI whitelist.

cn_add_callback
cn_del_callback
cn_netlink_send
dm_dirty_log_type_register
dm_dirty_log_type_unregister

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
kmod-cmirror-0.1.21-10.el5.x86_64.rpm
kmod-cmirror-xen-0.1.21-10.el5.x86_64.rpm

How reproducible:
Every time.

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.

Actual results:
Tainted kernel report.

Expected results:
Non-tainted kernel when using only Red Hat provided software.

Additional info:

Comment 1 Gary Case 2009-01-27 02:47:46 UTC

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.