39844b7e30
__setup() handlers should return 1 if the parameter is handled.
Returning 0 causes the entire string to be added to init's
environment strings (limited to 32 strings), unnecessarily polluting it.
Using the documented strings "TOMOYO_loader=string1" and
"TOMOYO_trigger=string2" causes an Unknown parameter message:
Unknown kernel command line parameters
"BOOT_IMAGE=/boot/bzImage-517rc5 TOMOYO_loader=string1 \
TOMOYO_trigger=string2", will be passed to user space.
and these strings are added to init's environment string space:
Run /sbin/init as init process
with arguments:
/sbin/init
with environment:
HOME=/
TERM=linux
BOOT_IMAGE=/boot/bzImage-517rc5
TOMOYO_loader=string1
TOMOYO_trigger=string2
With this change, these __setup handlers act as expected,
and init's environment is not polluted with these strings.
Fixes:
|
||
---|---|---|
.. | ||
policy | ||
.gitignore | ||
audit.c | ||
common.c | ||
common.h | ||
condition.c | ||
domain.c | ||
environ.c | ||
file.c | ||
gc.c | ||
group.c | ||
Kconfig | ||
load_policy.c | ||
Makefile | ||
memory.c | ||
mount.c | ||
network.c | ||
realpath.c | ||
securityfs_if.c | ||
tomoyo.c | ||
util.c |