Messages in this thread | | | Date | Sun, 13 May 2007 21:22:26 +0300 | From | Dan Aloni <> | Subject | Re: [PATCH] allow kernel module exclusion on load |
| |
On Sun, May 13, 2007 at 10:04:20PM +0400, Michael Tokarev wrote: > There are two issues (IMHO anyway), both are userspace. > > First is the ability blacklist the given module from bootloader. > My initramfs has it since the beginning - it allows a noload=xxx > paramerer (comma-separated list of module patterns, cumulative), > for exactly this purpose. I implemented modprobe in shell (not > using a binary from module-init-tools) for initramfs (it's some > 20 lines of shell code). Because of exactly that reason - on > certain systems i had a problem with certain drivers, resulting > in boot failures. Later on, this set of modules gets transformed > into a modprobe blacklist list. It's trivial to do. > > And second is what to do with direct insmod invocations in minimal > embedded system startup sequence. Well, minimal it or not, but > shell is present anyhow, so I don't see any problem with that, > either...
Yes, I guess a shell script can always look at /proc/cmdline with relatively minimal complexity.
Anyway, it all boils down to whether there's a developer demand for a userspace-independent way of blacklisting modules. Let's see if more people post their opinion so we can determine.
-- 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |