| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20070515082311.GA6816@ucw.cz> Date: Tue, 15 May 2007 08:23:11 +0000 From: Pavel Machek <pavel@....cz> To: Christoph Hellwig <hch@...radead.org>, Stephen Hemminger <shemminger@...ux-foundation.org>, Dan Aloni <da-x@...atomic.org>, Linux Kernel List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] allow kernel module exclusion on load 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@...atomic.org> wrote: > > > > > Kernel developers might find it useful for quickly getting out from some > > > rough debugging scenarios. > > > > > > Signed-off-by: Dan Aloni <da-x@...atomic.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? -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists