summaryrefslogtreecommitdiffstats
path: root/kernel/cgroup.c
diff options
context:
space:
mode:
authorPrarit Bhargava <prarit@redhat.com>2016-07-21 08:07:56 +0200
committerRusty Russell <rusty@rustcorp.com.au>2016-08-04 02:46:53 +0200
commitbe7de5f91fdc3a63ee01910c43f20db213445ce4 (patch)
treebce5a3b202a589e962cffa2f8dec3d58fbbddbc7 /kernel/cgroup.c
parentmodule: Do a WARN_ON_ONCE() for assert module mutex not held (diff)
downloadlinux-be7de5f91fdc3a63ee01910c43f20db213445ce4.tar.xz
linux-be7de5f91fdc3a63ee01910c43f20db213445ce4.zip
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>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions