diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2008-05-04 17:04:16 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2008-05-04 17:04:16 -0700 |
| commit | 826e4506a0acb6487910a5ebafe839f708a00e1c (patch) | |
| tree | 20cc66b6b38c0414930d85a8a9705a3a3eff8ddf /init/Kconfig | |
| parent | afa26be86b65a7183ceac29bdf1f51d6fc6932f0 (diff) | |
| download | linux-826e4506a0acb6487910a5ebafe839f708a00e1c.tar.gz linux-826e4506a0acb6487910a5ebafe839f708a00e1c.tar.bz2 linux-826e4506a0acb6487910a5ebafe839f708a00e1c.zip | |
Make forced module loading optional
The kernel module loader used to be much too happy to allow loading of
modules for the wrong kernel version by default. For example, if you
had MODVERSIONS enabled, but tried to load a module with no version
info, it would happily load it and taint the kernel - whether it was
likely to actually work or not!
Generally, such forced module loading should be considered a really
really bad idea, so make it conditional on a new config option
(MODULE_FORCE_LOAD), and make it default to off.
If somebody really wants to force module loads, that's their problem,
but we should not encourage it. Especially as it happened to me by
mistake (ie regular unversioned Fedora modules getting loaded) causing
lots of strange behavior.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'init/Kconfig')
| -rw-r--r-- | init/Kconfig | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/init/Kconfig b/init/Kconfig index 6a44defac3ec..f0e62e5ce0dc 100644 --- a/init/Kconfig +++ b/init/Kconfig @@ -825,6 +825,15 @@ menuconfig MODULES If unsure, say Y. +config MODULE_FORCE_LOAD + bool "Forced module loading" + depends on MODULES + default n + help + This option allows loading of modules even if that would set the + 'F' (forced) taint, due to lack of version info. Which is + usually a really bad idea. + config MODULE_UNLOAD bool "Module unloading" depends on MODULES |