summaryrefslogtreecommitdiffstats
path: root/Documentation/kernel-parameters.txt
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2014-06-11 19:09:14 -0400
committerLinus Torvalds <torvalds@linux-foundation.org>2014-06-11 19:09:14 -0400
commit4251c2a67011801caecd63671f26dd8c9aedb24c (patch)
tree06f659cb3f9e91fb2b8fc92791b5e021754e025e /Documentation/kernel-parameters.txt
parentc31c24b8251fd44962a9b0bf82c770653bf07f6e (diff)
parent4982223e51e8ea9d09bb33c8323b5ec1877b2b51 (diff)
Merge tag 'modules-next-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux
Pull module updates from Rusty Russell: "Most of this is cleaning up various driver sysfs permissions so we can re-add the perm check (we unified the module param and sysfs checks, but the module ones were stronger so we weakened them temporarily). Param parsing gets documented, and also "--" now forces args to be handed to init (and ignored by the kernel). Module NX/RO protections get tightened: we now set them before calling parse_args()" * tag 'modules-next-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux: module: set nx before marking module MODULE_STATE_COMING. samples/kobject/: avoid world-writable sysfs files. drivers/hid/hid-picolcd_fb: avoid world-writable sysfs files. drivers/staging/speakup/: avoid world-writable sysfs files. drivers/regulator/virtual: avoid world-writable sysfs files. drivers/scsi/pm8001/pm8001_ctl.c: avoid world-writable sysfs files. drivers/hid/hid-lg4ff.c: avoid world-writable sysfs files. drivers/video/fbdev/sm501fb.c: avoid world-writable sysfs files. drivers/mtd/devices/docg3.c: avoid world-writable sysfs files. speakup: fix incorrect perms on speakup_acntsa.c cpumask.h: silence warning with -Wsign-compare Documentation: Update kernel-parameters.tx param: hand arguments after -- straight to init modpost: Fix resource leak in read_dump()
Diffstat (limited to 'Documentation/kernel-parameters.txt')
-rw-r--r--Documentation/kernel-parameters.txt40
1 files changed, 25 insertions, 15 deletions
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index b9f67781c577..6eaa9cdb7094 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -1,27 +1,37 @@
1 Kernel Parameters 1 Kernel Parameters
2 ~~~~~~~~~~~~~~~~~ 2 ~~~~~~~~~~~~~~~~~
3 3
4The following is a consolidated list of the kernel parameters as implemented 4The following is a consolidated list of the kernel parameters as
5(mostly) by the __setup() macro and sorted into English Dictionary order 5implemented by the __setup(), core_param() and module_param() macros
6(defined as ignoring all punctuation and sorting digits before letters in a 6and sorted into English Dictionary order (defined as ignoring all
7case insensitive manner), and with descriptions where known. 7punctuation and sorting digits before letters in a case insensitive
8 8manner), and with descriptions where known.
9Module parameters for loadable modules are specified only as the 9
10parameter name with optional '=' and value as appropriate, such as: 10The kernel parses parameters from the kernel command line up to "--";
11 11if it doesn't recognize a parameter and it doesn't contain a '.', the
12 modprobe usbcore blinkenlights=1 12parameter gets passed to init: parameters with '=' go into init's
13 13environment, others are passed as command line arguments to init.
14Module parameters for modules that are built into the kernel image 14Everything after "--" is passed as an argument to init.
15are specified on the kernel command line with the module name plus 15
16'.' plus parameter name, with '=' and value if appropriate, such as: 16Module parameters can be specified in two ways: via the kernel command
17 17line with a module name prefix, or via modprobe, e.g.:
18 usbcore.blinkenlights=1 18
19 (kernel command line) usbcore.blinkenlights=1
20 (modprobe command line) modprobe usbcore blinkenlights=1
21
22Parameters for modules which are built into the kernel need to be
23specified on the kernel command line. modprobe looks through the
24kernel command line (/proc/cmdline) and collects module parameters
25when it loads a module, so the kernel command line can be used for
26loadable modules too.
19 27
20Hyphens (dashes) and underscores are equivalent in parameter names, so 28Hyphens (dashes) and underscores are equivalent in parameter names, so
21 log_buf_len=1M print-fatal-signals=1 29 log_buf_len=1M print-fatal-signals=1
22can also be entered as 30can also be entered as
23 log-buf-len=1M print_fatal_signals=1 31 log-buf-len=1M print_fatal_signals=1
24 32
33Double-quotes can be used to protect spaces in values, e.g.:
34 param="spaces in here"
25 35
26This document may not be entirely up to date and comprehensive. The command 36This document may not be entirely up to date and comprehensive. The command
27"modinfo -p ${modulename}" shows a current list of all parameters of a loadable 37"modinfo -p ${modulename}" shows a current list of all parameters of a loadable