mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "christophe barbé" <christophe.barbe@lineo.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.9-ac6
Date: Wed, 5 Sep 2001 15:23:12 +0200	[thread overview]
Message-ID: <20010905152312.A11004@pc8.lineo.fr> (raw)
In-Reply-To: <20010905145039.A10655@pc8.lineo.fr> <1269703968.999699248@[169.254.198.40]>
In-Reply-To: <1269703968.999699248@[169.254.198.40]>; from linux-kernel@alex.org.uk on mer, sep 05, 2001 at 15:14:09 +0200


Le mer, 05 sep 2001 15:14:09, Alex Bligh - linux-kernel a écrit :
> > Would it not be possible with your scheme to package a closed source
> > driver in an open source wrapper driver and then defeat your tainting
> > technique.
> 
> It would also be theoretically possible for an evil driver merchant
> to twiddle the flag back via /dev/kmem (for instance). Or load the
> module by manipulation of /dev/kmem. Or for the bug-reporting user
> to patch their kernel so that the flag never got set and hence
> disguise the presence of an nvidia driver (etc.) in a misguided
> attempt to wangle support out of Alan et al.
> 
> However, I understood the point of the exercize to be a first pass
> hueristic to flag bug reports from systems running modules for
> which Alan and others haven't got, and can't get the source. It's
> not going to be perfect (see above), but equally doesn't need to be.
> I'm sure users do all sorts of other 'well don't do that, then'
> stuff which wastes the time of those reading bug reports.

Yes I agree that's not easy and certainly not the goal to avoid this kind
of thing.

Btw I was thinking about a real case: I use in my laptop the lucent driver
for their winmodem chipset. This driver is closed source but we use it
relinked with proper opensource code. This avoid the use of 'insmod -f' and
most of the bug (caused by missing symbols) but you can not trust the
resulting module.

Christophe

> --
> Alex Bligh
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 
-- 
Christophe Barbé
Software Engineer - christophe.barbe@lineo.fr
Lineo France - Lineo High Availability Group
42-46, rue Médéric - 92110 Clichy - France
phone (33).1.41.40.02.12 - fax (33).1.41.40.02.01
http://www.lineo.com

  reply	other threads:[~2001-09-05 13:23 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03  1:50 Alan Cox
2001-09-03  2:51 ` Keith Owens
2001-09-03  3:08   ` Dave Jones
2001-09-03 13:05 ` Andrea Arcangeli
2001-09-03 13:21   ` Alan Cox
2001-09-05  1:51   ` Keith Owens
2001-09-05  3:30     ` David Schwartz
2001-09-05  3:50       ` Keith Owens
2001-09-05  5:16         ` David Schwartz
2001-09-05  5:39           ` Alan Shutko
2001-09-05 18:46             ` David Schwartz
2001-09-05  5:52           ` H. Peter Anvin
2001-09-05  5:56           ` Aaron Lehmann
2001-09-05  7:03             ` David Schwartz
2001-09-05  7:09               ` David Schwartz
2001-09-05  9:50                 ` Alex Bligh - linux-kernel
2001-09-05  9:57                   ` David Schwartz
2001-09-05 12:50                     ` christophe barbé
2001-09-05 13:06                       ` Alan Cox
2001-09-05 13:14                       ` Alex Bligh - linux-kernel
2001-09-05 13:23                         ` christophe barbé [this message]
2001-09-05 14:05                       ` Henning P. Schmiedehausen
2001-09-05  7:18               ` Aaron Lehmann
2001-09-05  7:19                 ` David Schwartz
2001-09-05  9:41               ` Justin Guyett
2001-09-05  9:53                 ` David Schwartz
2001-09-05 10:21                   ` Justin Guyett
2001-09-05 11:55                   ` Alan Cox
2001-09-05 18:46                     ` David Schwartz
2001-09-05 18:54                       ` Alan Cox
2001-09-05 22:09                       ` Linux 2.4.9-ac6 (really about tainting) David Schwartz
2001-09-05 12:07       ` Linux 2.4.9-ac6 Alan Cox
2001-09-05 12:16         ` Arjan van de Ven
2001-09-05 12:23           ` Jan-Benedict Glaw
2001-09-05 14:36 Thomas Foerster
2001-09-06 19:23 ` Camiel Vanderhoeven
2001-09-06 20:14   ` Alan Cox

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=20010905152312.A11004@pc8.lineo.fr \
    --to=christophe.barbe@lineo.fr \
    --cc=linux-kernel@vger.kernel.org \
    /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®