Skip to contentSkip to conversation

show all modules which taint the kernel ?

DISCUSSION [email protected] 2 participants 2 messages Sep 17, 2006

lore
Share & tools
lore
#0 lore raw

if there is a "contaminant" inside the kernel, why should one see this only when it`s being inserted (i.e. usually at boot time) ?

i don`t know about the "nvidia(P)..." thing, but i would find it really useful to be able to easily distinguish between the "good" and the "not belonging to this kernel" modules.

i have seem several discussions about "modules which taint the kernel are evil" - so why not pillory them by listing appropriate information with lsmod ?

Quoted 12 lines

-----Ursprüngliche Nachricht-----
Von: Lee Revell <[email protected]>
Gesendet: 17.09.06 02:01:05
An: Dave Jones <[email protected]>
CC: [email protected]
Betreff: Re: show all modules which taint the kernel ?

Quoted 3 lines · Dave Jones
Quoted 1 line · On Sat, Sep 16, 2006 at 08:58:20PM +0200, [email protected] wrote:

but that "Modules linked in: radeon(U) drm(U) ipv6(U) autofs4(U)...." message has been reported to originate from a fc5 (fedora) kernel. fedora probably also using that novell/suse extension ?

Quoted 8 lines
Quoted 2 lines

Different. The Fedora kernel reports U for modules that weren't shipped with the Fedora kernel. (It uses gpg signed modules).

Vendor kernels aside, would it be useful for mainline to report this information - something like nvidia(P) in the module list?

Lee

_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066

#1 lore raw
Quoted 10 lines · On Sunday 17 September 2006 10:34, [email protected] wrote:

if there is a "contaminant" inside the kernel, why should one see this only when it`s being inserted (i.e. usually at boot time) ?

i don`t know about the "nvidia(P)..." thing, but i would find it really useful to be able to easily distinguish between the "good" and the "not belonging to this kernel" modules.

i have seem several discussions about "modules which taint the kernel are evil" - so why not pillory them by listing appropriate information with lsmod ?

I think the point being made is that we don't want to confuse this with vendors disclaiming support for non-shipped kernel modules. Vanilla kernels shouldn't consider GPL modules to be "unsupported" just because they aren't shipped or "digitally signed"; however we certainly should be highlighting the use of proprietary modules (which are obviously impossible to debug).

I agree with Lee, there should be some more black marks on proprietary drivers than there are currently.

Signature · 5 lines
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.