From: "Nigel Cunningham" <ncunningham@linuxmail.org>
To: "Chris Siebenmann" <cks@utcc.utoronto.ca>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: What does tainting actually mean?
Date: Wed, 28 Apr 2004 16:18:44 +1000 [thread overview]
Message-ID: <opr65k5ivcshwjtr@laptop-linux.wpcb.org.au> (raw)
In-Reply-To: <04Apr28.020259edt.41801@gpu.utcc.utoronto.ca>
Hi.
On Wed, 28 Apr 2004 02:02:55 -0400, Chris Siebenmann
<cks@utcc.utoronto.ca> wrote:
> What happens when a binary module thinks it knows the size of a
> structure and is wrong? What happens when a binary module has a
> concurrency problem, in any of the many forms they manifest in the Linux
> kernel?
Good points. It could be really difficult to trace the cause of those
issues. But hard/too much effort != impossible. For every entry point to
the module we have a known state of the system prior to and after the
call. We could potentially checksum the whole of memory before and after
and find out exactly what the module has changed.
Anyway, I'm going to drop this conversation now. Work to do :>
Nigel
--
Nigel Cunningham
C/- Westminster Presbyterian Church Belconnen
61 Templeton Street, Cook, ACT 2614, Australia.
+61 (2) 6251 7727 (wk)
next parent reply other threads:[~2004-04-28 6:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <04Apr28.020259edt.41801@gpu.utcc.utoronto.ca>
2004-04-28 6:18 ` Nigel Cunningham [this message]
2004-04-28 10:37 ` Bartlomiej Zolnierkiewicz
2004-04-28 4:00 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
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
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=opr65k5ivcshwjtr@laptop-linux.wpcb.org.au \
--to=ncunningham@linuxmail.org \
--cc=cks@utcc.utoronto.ca \
--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®