mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: devzero@web.de
Cc: Dave Jones <davej@redhat.com>, Lee Revell <rlrevell@joe-job.com>,
	linux-kernel@vger.kernel.org
Subject: Re: show all modules which taint the kernel ?
Date: Sun, 17 Sep 2006 18:06:45 +0100	[thread overview]
Message-ID: <200609171806.45215.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <1313891898@web.de>

On Sunday 17 September 2006 10:34, devzero@web.de 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.

-- 
Cheers,
Alistair.

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

  reply	other threads:[~2006-09-17 17:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-17  9:34 devzero
2006-09-17 17:06 ` Alistair John Strachan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-16 18:58 devzero
2006-09-16 23:46 ` Dave Jones
2006-09-17  0:07   ` Lee Revell
2006-09-16 10:25 devzero
2006-09-16 16:27 ` Lee Revell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200609171806.45215.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=davej@redhat.com \
    --cc=devzero@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®