From: Stefan Smietanowski <stesmi@stesmi.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Nigel Cunningham <ncunningham@linuxmail.org>,
Jurriaan <thunder7@xs4all.nl>,
linux-kernel@vger.kernel.org
Subject: Re: What does tainting actually mean?
Date: Mon, 03 May 2004 20:50:50 +0200 [thread overview]
Message-ID: <4096948A.4010708@stesmi.com> (raw)
In-Reply-To: <20040503124555.GB1188@openzaurus.ucw.cz>
Hi Pavel.
>>Is that true? We can see where the oops occurs. If it's in the
>>module, nothing more needs to be said. If it's in the kernel itself,
>>we can check our source. We could check all the calls the module
>
>
> We *could* do it, but it would take too much time and we
> have better stuff to do.
And we don't know if that module didn't overwrite memory (nVidia ..)
or anything else either. The the oops is really useless.
Of course, those cases are difficult to debug ANYWAY even if you have
the source but if it's binary you can't do squat.
// Stefan
next prev parent reply other threads:[~2004-05-03 18:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 4:00 What does tainting actually mean? Nigel Cunningham
2004-04-28 4:27 ` Jurriaan
2004-04-28 4:30 ` Nigel Cunningham
2004-04-28 5:19 ` Chris Friesen
2004-04-28 5:18 ` Nigel Cunningham
2004-04-28 12:10 ` Theodore Ts'o
2004-04-28 12:48 ` Måns Rullgård
2004-04-28 13:04 ` Muli Ben-Yehuda
2004-04-28 13:27 ` Måns Rullgård
2004-04-28 14:22 ` Muli Ben-Yehuda
2004-04-28 15:56 ` Joseph Pingenot
2004-04-28 16:01 ` Valdis.Kletnieks
2004-05-03 12:45 ` Pavel Machek
2004-05-03 18:50 ` Stefan Smietanowski [this message]
2004-04-28 5:51 ` Karim Yaghmour
2004-04-28 6:51 ` Keith Duthie
2004-04-28 10:26 ` Ville Herva
2004-05-06 15:25 ` Anthony de Boer
[not found] <04Apr28.020259edt.41801@gpu.utcc.utoronto.ca>
2004-04-28 6:18 ` Nigel Cunningham
2004-04-28 10:37 ` Bartlomiej Zolnierkiewicz
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=4096948A.4010708@stesmi.com \
--to=stesmi@stesmi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.org \
--cc=pavel@ucw.cz \
--cc=thunder7@xs4all.nl \
/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