From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Adrian Bunk <bunk@stusta.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
Ingo Molnar <mingo@elte.hu>,
Christoph Hellwig <hch@infradead.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: Please revert 21564fd2a3deb48200b595332f9ed4c9f311f2a7
Date: Mon, 09 Jul 2007 06:55:03 -0700 [thread overview]
Message-ID: <46923E37.9010303@goop.org> (raw)
In-Reply-To: <20070709105123.1df728b2@the-village.bc.nu>
Alan Cox wrote:
> 2.6.22's behaviour is the bug. 2.6.21 you couldn't load random binary
> crap into the kernel without logging a taint. 2.6.22 you can. This means
> every single 2.6.22 bug report has to be assumed to be caused by binary
> module crap as a starting point which slows down debug immensely.
Er, what? What do you mean by "load random binary crap"? Are you
worried that a malicious kernel module might modify paravirt_ops? How
is that different from a malicious module doing any of the infinite
other things a malicious module can do? A module will only register a
taint if its playing by the rules anyway, and a module playing by the
rules won't touch paravirt_ops directly.
J
prev parent reply other threads:[~2007-07-09 13:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 21:42 Please revert 21564fd2a3deb48200b595332f9ed4c9f311f2a7 Adrian Bunk
2007-06-18 4:43 ` Jeremy Fitzhardinge
2007-07-08 22:44 ` Adrian Bunk
2007-07-08 23:02 ` Andi Kleen
2007-07-08 23:17 ` Adrian Bunk
2007-07-09 9:39 ` Andi Kleen
2007-07-09 10:06 ` Alan Cox
2007-07-09 10:35 ` Andi Kleen
2007-07-09 9:32 ` Alan Cox
2007-07-09 9:39 ` Andi Kleen
2007-07-09 14:06 ` Jeremy Fitzhardinge
2007-07-09 2:46 ` Jeremy Fitzhardinge
2007-07-09 9:51 ` Alan Cox
2007-07-09 13:55 ` Jeremy Fitzhardinge [this message]
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=46923E37.9010303@goop.org \
--to=jeremy@goop.org \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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