modules: Add kernel parameter to blacklist modules
authorPrarit Bhargava <prarit@redhat.com>
Thu, 21 Jul 2016 06:07:56 +0000 (15:37 +0930)
committerRusty Russell <rusty@rustcorp.com.au>
Thu, 4 Aug 2016 00:46:53 +0000 (10:16 +0930)
commitbe7de5f91fdc3a63ee01910c43f20db213445ce4
treebce5a3b202a589e962cffa2f8dec3d58fbbddbc7
parent9502514f2808d29f6f2afa1c410e7808898dede1
modules: Add kernel parameter to blacklist modules

Blacklisting a module in linux has long been a problem.  The current
procedure is to use rd.blacklist=module_name, however, that doesn't
cover the case after the initramfs and before a boot prompt (where one
is supposed to use /etc/modprobe.d/blacklist.conf to blacklist
runtime loading). Using rd.shell to get an early prompt is hit-or-miss,
and doesn't cover all situations AFAICT.

This patch adds this functionality of permanently blacklisting a module
by its name via the kernel parameter module_blacklist=module_name.

[v2]: Rusty, use core_param() instead of __setup() which simplifies
things.

[v3]: Rusty, undo wreckage from strsep()

[v4]: Rusty, simpler version of blacklisted()

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-doc@vger.kernel.org
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Documentation/kernel-parameters.txt
kernel/module.c
This page took 0.02742 seconds and 5 git commands to generate.