Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 40453c4f authored by Mark Rutland's avatar Mark Rutland Committed by Linus Torvalds
Browse files

kcov: improve CONFIG_ARCH_HAS_KCOV help text 

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: default avatarMark Rutland <mark.rutland@arm.com>
Acked-by: default avatarDmitry Vyukov <dvyukov@google.com>
Cc: Kees Cook <keescook@chromium.org>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent 3b991208

lib/Kconfig.debug

+3 −3
Original line number Diff line number Diff line
@@ -753,9 +753,9 @@ endmenu # "Memory Debugging" 
config ARCH_HAS_KCOV

	bool

	help

	  KCOV does not have any arch-specific code, but currently it is enabled

	  only for x86_64. KCOV requires testing on other archs, and most likely

	  disabling of instrumentation for some early boot code.

	  An architecture should select this when it can successfully

	  build and run with CONFIG_KCOV. This typically requires

	  disabling instrumentation for some early boot code.



config CC_HAS_SANCOV_TRACE_PC

	def_bool $(cc-option,-fsanitize-coverage=trace-pc)