kdb: Censor attempts to set PROMPT without ENABLE_MEM_READ
authorDaniel Thompson <daniel.thompson@linaro.org>
Thu, 13 Feb 2020 15:16:40 +0000 (15:16 +0000)
committerDaniel Thompson <daniel.thompson@linaro.org>
Wed, 1 Apr 2020 15:59:11 +0000 (16:59 +0100)
commitad99b5105c0823ff02126497f4366e6a8009453e
tree44e3f94cbac26b7e9208a2b4b1cabb30c77acabc
parentd228bee8201a7ea77c414f1298b2f572f42c6113
kdb: Censor attempts to set PROMPT without ENABLE_MEM_READ

Currently the PROMPT variable could be abused to provoke the printf()
machinery to read outside the current stack frame. Normally this
doesn't matter becaues md is already a much better tool for reading
from memory.

However the md command can be disabled by not setting KDB_ENABLE_MEM_READ.
Let's also prevent PROMPT from being modified in these circumstances.

Whilst adding a comment to help future code reviewers we also remove
the #ifdef where PROMPT in consumed. There is no problem passing an
unused (0) to snprintf when !CONFIG_SMP.
argument

Reported-by: Wang Xiayang <xywang.sjtu@sjtu.edu.cn>
Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
kernel/debug/kdb/kdb_main.c