From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Jon Masters <jonathan@jonmasters.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: changeset: Make forced module loading optional
Date: Tue, 6 May 2008 04:42:12 +1000 [thread overview]
Message-ID: <200805060442.12440.rusty@rustcorp.com.au> (raw)
In-Reply-To: <alpine.LFD.1.10.0805050957590.32269@woody.linux-foundation.org>
On Tuesday 06 May 2008 03:07:03 Linus Torvalds wrote:
> On Mon, 5 May 2008, Rusty Russell wrote:
> > BTW, for the peanut gallery: I don't recommend modversions: it's not
> > reliable in detecting all differences, nor being stable when there are no
> > real differences.
...
> So I agree that modversions is not "reliable", but I think that the
> alternative is often even *less* reliable, so I find the "don't recommend
> modversions" comment to be pretty debatable.
Kids: do not shove random modules into your kernel. Just because Linus does
something doesn't make it a good idea. modversions tries to be clever, but
don't count on it; you want module signing for this (where did those patches
go?)
BTW, I'm fascinated and a little nausiated that you ignore initrds. We've
moved half the kernel brains to userspace with udev, initrd and modules; it's
really unfair that you're not sharing all that why-won't-my-machine-boot
love.
Cheers,
Rusty.
next prev parent reply other threads:[~2008-05-05 18:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 4:55 changeset: Make forced module loading optional Rusty Russell
2008-05-05 5:05 ` Linus Torvalds
2008-05-05 5:35 ` Rusty Russell
2008-05-05 17:07 ` Linus Torvalds
2008-05-05 18:42 ` Rusty Russell [this message]
2008-05-05 19:47 ` David Miller
2008-05-05 6:43 ` Jan Engelhardt
2008-05-05 14:37 ` Linus Torvalds
2008-05-05 14:50 ` Jeff Garzik
2008-05-05 15:01 ` Linus Torvalds
2008-05-05 15:08 ` Linus Torvalds
2008-05-05 15:32 ` Dave Jones
2008-05-05 15:48 ` Linus Torvalds
2008-05-05 16:01 ` Jan Engelhardt
2008-05-05 15:57 ` Alan Cox
2008-05-05 6:35 ` Jan Engelhardt
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=200805060442.12440.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--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