diff options
author | 2022-02-22 13:45:33 -0800 | |
---|---|---|
committer | 2022-02-24 07:45:07 +0900 | |
commit | 39844b7e3084baecef52d1498b5fa81afa2cefa9 (patch) | |
tree | 0d7566ad60f504577f17e95b3500631ca8a8a46e /arch/sh/mm | |
parent | Merge branch 'for-5.17-fixes' of git://git.kernel.org/pub/scm/linux/kernel/gi... (diff) | |
download | linux-39844b7e3084baecef52d1498b5fa81afa2cefa9.tar.gz linux-39844b7e3084baecef52d1498b5fa81afa2cefa9.tar.bz2 linux-39844b7e3084baecef52d1498b5fa81afa2cefa9.zip |
TOMOYO: fix __setup handlers return values
__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: 0e4ae0e0dec63 ("TOMOYO: Make several options configurable.")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Reported-by: Igor Zhbanov <i.zhbanov@omprussia.ru>
Link: https://lore.kernel.org/r/64644a2f-4a20-bab3-1e15-3b2cdd0defe3@omprussia.ru
Cc: James Morris <jmorris@namei.org>
Cc: Kentaro Takeda <takedakn@nttdata.co.jp>
Cc: tomoyo-dev-en@lists.osdn.me
Cc: "Serge E. Hallyn" <serge@hallyn.com>
Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Diffstat (limited to 'arch/sh/mm')
0 files changed, 0 insertions, 0 deletions