[lkml]   [2007]   [May]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [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
da-x (at), dan (at)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-05-13 20:25    [W:0.062 / U:0.044 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site