kernel_optimize_test/kernel/kcsan
Marco Elver b738f6169f kcsan: Introduce kcsan_value_change type
Introduces kcsan_value_change type, which explicitly points out if we
either observed a value-change (TRUE), or we could not observe one but
cannot rule out a value-change happened (MAYBE). The MAYBE state can
either be reported or not, depending on configuration preferences.

A follow-up patch introduces the FALSE state, which should never be
reported.

No functional change intended.

Acked-by: John Hubbard <jhubbard@nvidia.com>
Signed-off-by: Marco Elver <elver@google.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2020-03-21 09:44:03 +01:00
..
atomic.h kcsan: Prefer __always_inline for fast-path 2020-03-21 09:40:19 +01:00
core.c kcsan: Introduce kcsan_value_change type 2020-03-21 09:44:03 +01:00
debugfs.c kcsan: Add test to generate conflicts via debugfs 2020-03-21 09:43:30 +01:00
encoding.h kcsan: Prefer __always_inline for fast-path 2020-03-21 09:40:19 +01:00
kcsan.h kcsan: Introduce kcsan_value_change type 2020-03-21 09:44:03 +01:00
Makefile kcsan, ubsan: Make KCSAN+UBSAN work together 2020-01-07 07:47:23 -08:00
report.c kcsan: Introduce kcsan_value_change type 2020-03-21 09:44:03 +01:00
test.c kcsan: Fix 0-sized checks 2020-03-21 09:42:42 +01:00