From: Adrian Bunk <bunk@stusta.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: 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>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Please revert 21564fd2a3deb48200b595332f9ed4c9f311f2a7
Date: Sun, 17 Jun 2007 23:42:31 +0200 [thread overview]
Message-ID: <20070617214231.GA3588@stusta.de> (raw)
Linus, please revert commit 21564fd2a3deb48200b595332f9ed4c9f311f2a7
It's not acceptable since illegal modules should definitely not get
write access to paravirt_ops.
Andi forwarded it although the following people had already NAK'ed it:
- Christoph Hellwig [1]
- Peter Zijlstra [2]
- Alan Cox [3]
Considering that Andi forwarded it 2 days after he himself said a
different solution was pending [4] I assume he mistakenly sent it for
inclusion in your tree.
Reverting is safe since it simply re-establishes the 2.6.21 status quo.
cu
Adrian
[1] http://lkml.org/lkml/2007/4/30/132
[2] http://lkml.org/lkml/2007/4/30/197
[3] http://lkml.org/lkml/2007/4/30/237
[4] http://lkml.org/lkml/2007/4/30/335
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next reply other threads:[~2007-06-17 21:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 21:42 Adrian Bunk [this message]
2007-06-18 4:43 ` Please revert 21564fd2a3deb48200b595332f9ed4c9f311f2a7 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
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=20070617214231.GA3588@stusta.de \
--to=bunk@stusta.de \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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