Bug 236424
Summary: | [RHEL5 RT] GPL / NonGPL Module testing fails on x86_64 | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Jeff Burke <jburke> |
Component: | realtime-kernel | Assignee: | Don Zickus <dzickus> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1.0 | CC: | dhowells, dzickus, jcm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
URL: | http://rhts.lab.boston.redhat.com/cgi-bin/rhts/recipes.cgi?id=73494 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-02-12 18:41:21 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: | |||
Bug Depends On: | 253476 | ||
Bug Blocks: |
Description
Jeff Burke
2007-04-13 20:17:31 UTC
This is failing in the latest kernel 2.6.21-11.el5rt: /kernel/drivers/3rd-party Completed - Fail GPLModule Fail 0 NonGPLModule Fail 0 BadModuleSign Pass 0 GoodModuleSign Pass 0 http://rhts.lab.boston.redhat.com/cgi-bin/rhts/jobs.cgi?id=773&type=Single Recipe 2854 This may be due to the test script making assumptions about its operating environment: (1) /proc/sys/kernel/print-fatal-signals does not appear to exist in the kernel specified, yet CheckUnsignModule() attempts to make use of it. (2) The killme.sh script does not appear to leave anything in the dmesg log, but CheckUnsignModule() appears to rely on it saying something. What kernel were these scripts meant to test? These scripts were designed for RHEL-5. The execshield patch puts the print-fatal-signals functionality into the kernel. So yeah, if the kernel doesn't have print-fatal-signal, the test won't do much. Unless someone has another way to detect if a 'bad' kernel module tainted the kernel using a userspace app? Like 253476 perhaps. Jon. Jon, Do we have any additional data on this issue? Are we going to try and fix it for RT? Jeff Jeff, This test is really RHEL-5 specific. We should be able to modify it to utilize the output of /proc/modules now. Upstream added a patch to display the taint flags to that proc file. I am working with Jon to backport this to RHEL-5 so we can better test across all the arches. Once those changes are in, we can modify the script to take advantage of the proc file and then the test should automatically become forward compatible (with RT/RHEL-6, etc). Where do we stand on this bug, wrt RT? Clark, As discusses on IRC and verbally. This test is of no value to the RT kernel Jeff |