UPSTREAM: kcov: improve CONFIG_ARCH_HAS_KCOV help text

(Upstream commit 40453c4f9bb6d166a56a102a8c51dd24b0801557.)

The help text for CONFIG_ARCH_HAS_KCOV is stale, and describes the
feature as being enabled only for x86_64, when it is now enabled for
several architectures, including arm, arm64, powerpc, and s390.

Let's remove that stale help text, and update it along the lines of hat
for ARCH_HAS_FORTIFY_SOURCE, better describing when an architecture
should select CONFIG_ARCH_HAS_KCOV.

Link: http://lkml.kernel.org/r/20190412102733.5154-1-mark.rutland@arm.com
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Acked-by: Dmitry Vyukov <dvyukov@google.com>
Cc: Kees Cook <keescook@chromium.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
Bug: 147413187
Change-Id: If1a6cce383c704fc96ea9a267459b665d32fb8bd
This commit is contained in:
Mark Rutland 2019-04-18 17:50:37 -07:00 committed by Alistair Delva
parent 3a3cd9cd27
commit 9b5f12321a

View File

@ -736,9 +736,9 @@ endmenu # "Memory Debugging"
config ARCH_HAS_KCOV config ARCH_HAS_KCOV
bool bool
help help
KCOV does not have any arch-specific code, but currently it is enabled An architecture should select this when it can successfully
only for x86_64. KCOV requires testing on other archs, and most likely build and run with CONFIG_KCOV. This typically requires
disabling of instrumentation for some early boot code. disabling instrumentation for some early boot code.
# Upstream uses $(cc-option, -fsanitize-coverage=trace-pc), which requires # Upstream uses $(cc-option, -fsanitize-coverage=trace-pc), which requires
# cc-option support. Here we instead check CC in scripts/Makefile.kcov. # cc-option support. Here we instead check CC in scripts/Makefile.kcov.