public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Aloni <da-x@monatomic.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Christoph Hellwig <hch@infradead.org>,
	Stephen Hemminger <shemminger@linux-foundation.org>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] allow kernel module exclusion on load
Date: Wed, 16 May 2007 19:51:07 +0300	[thread overview]
Message-ID: <20070516165107.GA13190@localdomain> (raw)
In-Reply-To: <20070515082311.GA6816@ucw.cz>

On Tue, May 15, 2007 at 08:23:11AM +0000, Pavel Machek wrote:
> On Sun 2007-05-13 19:20:35, Christoph Hellwig wrote:
> > On Sun, May 13, 2007 at 09:23:52AM -0700, Stephen Hemminger wrote:
> > > On Sun, 13 May 2007 16:25:17 +0300
> > > Dan Aloni <da-x@monatomic.org> wrote:
> > > 
> > > > Kernel developers might find it useful for quickly getting out from some 
> > > > rough debugging scenarios.
> > > > 
> > > > Signed-off-by: Dan Aloni <da-x@monatomic.org>
> > > > 
> > > 
> > > There is already the modprobe blacklist ability in user space.
> > 
> > doesn't really help if hotplug loads a broken module before you're getting
> > a login prompt.  So while this is a bit of a hack I'm all in favour of this.
> > (Especially as I got hit by this issue again yesterday)
> 
> It is quite a bick hack. Unknown kernel parameters are passed to init,
> can we just make modprobe parse that?

We can, and then we also have to patch busybox's own fork of modprobe
and every other code out there that does the same thing (not so much, 
but still).

-- 
Dan Aloni
XIV LTD, http://www.xivstorage.com
da-x (at) monatomic.org, dan (at) xiv.co.il

  reply	other threads:[~2007-05-16 16:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-13 13:25 [PATCH] allow kernel module exclusion on load Dan Aloni
2007-05-13 16:23 ` Stephen Hemminger
2007-05-13 17:05   ` Nikita V. Youshchenko
2007-05-13 17:15   ` Dan Aloni
2007-05-13 18:04     ` Michael Tokarev
2007-05-13 18:22       ` Dan Aloni
2007-05-13 18:32         ` Michael Tokarev
2007-05-13 18:20   ` Christoph Hellwig
2007-05-13 18:39     ` Michael Tokarev
2007-05-15  8:23     ` Pavel Machek
2007-05-16 16:51       ` Dan Aloni [this message]
2007-05-16 19:33         ` Pavel Machek
2007-05-16 21:09           ` Dan Aloni
2007-05-16 22:00             ` Randy Dunlap
2007-05-15 13:07     ` Andi Kleen
2007-05-14 20:23 ` Valdis.Kletnieks
2007-05-15  8:48   ` Dan Aloni

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=20070516165107.GA13190@localdomain \
    --to=da-x@monatomic.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=shemminger@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