The following commit has been merged into the locking/kcsan branch of tip:

Commit-ID:     eba9c444d34c9f10cbb463329c2c8e14f2adff25
Gitweb:        
https://git.kernel.org/tip/eba9c444d34c9f10cbb463329c2c8e14f2adff25
Author:        Ingo Molnar <mi...@kernel.org>
AuthorDate:    Mon, 13 Apr 2020 11:03:05 +02:00
Committer:     Paul E. McKenney <paul...@kernel.org>
CommitterDate: Mon, 27 Apr 2020 11:10:02 -07:00

Improve KCSAN documentation a bit

This commit simplifies and clarifies the highest level KCSAN Kconfig
help text.

Signed-off-by: Ingo Molnar <mi...@kernel.org>
Signed-off-by: Paul E. McKenney <paul...@kernel.org>
---
 lib/Kconfig.kcsan | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/lib/Kconfig.kcsan b/lib/Kconfig.kcsan
index 0f1447f..689b6b8 100644
--- a/lib/Kconfig.kcsan
+++ b/lib/Kconfig.kcsan
@@ -4,17 +4,18 @@ config HAVE_ARCH_KCSAN
        bool
 
 menuconfig KCSAN
-       bool "KCSAN: dynamic race detector"
+       bool "KCSAN: dynamic data race detector"
        depends on HAVE_ARCH_KCSAN && DEBUG_KERNEL && !KASAN
        select STACKTRACE
        help
-         The Kernel Concurrency Sanitizer (KCSAN) is a dynamic race detector,
-         which relies on compile-time instrumentation, and uses a
-         watchpoint-based sampling approach to detect races.
+         The Kernel Concurrency Sanitizer (KCSAN) is a dynamic
+         data-race detector that relies on compile-time instrumentation.
+         KCSAN uses a watchpoint-based sampling approach to detect races.
 
-         KCSAN's primary purpose is to detect data races. KCSAN can also be
-         used to check properties, with the help of provided assertions, of
-         concurrent code where bugs do not manifest as data races.
+         While KCSAN's primary purpose is to detect data races, it
+         also provides assertions to check data access constraints.
+         These assertions can expose bugs that do not manifest as
+         data races.
 
          See <file:Documentation/dev-tools/kcsan.rst> for more details.
 

Reply via email to