| 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: <20070513171555.GA27920@localdomain> Date: Sun, 13 May 2007 20:15:55 +0300 From: Dan Aloni <da-x@...atomic.org> To: Stephen Hemminger <shemminger@...ux-foundation.org> Cc: Linux Kernel List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] allow kernel module exclusion on load 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. Yes, however the point here is that you can easily (and temporarily) blacklist a module *manually* from the boot loader without needing to actually perform a complete and successful boot. Using modprobe's blacklist requires editing /etc files, and it also doesn't apply for initrd/initramfs or other system/distribution-specific scripts that would do hardcoded sequential insmod invocations (for example on embedded systems that require minimal userspace complexity). -- Dan Aloni XIV LTD, http://www.xivstorage.com da-x (at) monatomic.org, dan (at) xiv.co.il - 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