Bug 149904 - Setting tainted flag through linux module
Summary: Setting tainted flag through linux module
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: RC 4
Hardware: Other Other
: P5 - None : Major
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-10 10:59 UTC by Klaus Singvogel
Modified: 2006-02-10 11:04 UTC (History)
0 users

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Klaus Singvogel 2006-02-10 10:59:33 UTC 
I made the security update of my SuSE Linux 10.0 box and noticed that I get the tainted flag through a Novell/Linux distributed module: fscpos

I think it is important that this does not happen ==> Major

------------------- snip ---------------------- snip -------------------------
Here is /var/log/warn:
Feb 10 11:19:55 linux kernel: fscpos: module not supported by Novell, setting U taint flag.

prompt> locate fscpos
/lib/modules/2.6.13-15.7-default/kernel/drivers/hwmon/fscpos.ko
/usr/share/doc/packages/sensors/chips/fscpos

prompt> rpm -qf /lib/modules/2.6.13-15.8-default/kernel/drivers/hwmon/fscpos.ko
kernel-default-2.6.13-15.8
Comment 1 Olaf Kirch 2006-02-10 11:04:32 UTC 
No, this is intentional.

Admittedly, the distinction of supported vs unsupported modules doesn't
make a lot of a difference on the box, but for SLES it's essential.