kernel_optimize_test/kernel/kcsan
Marco Elver 3a5b45e503 kcsan: Fix misreporting if concurrent races on same address
If there are at least 4 threads racing on the same address, it can
happen that one of the readers may observe another matching reader in
other_info. To avoid locking up, we have to consume 'other_info'
regardless, but skip the report. See the added comment for more details.

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:43:41 +01:00
..
atomic.h kcsan: Prefer __always_inline for fast-path 2020-03-21 09:40:19 +01:00
core.c kcsan: Expose core configuration parameters as module params 2020-03-21 09:43:35 +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_ACCESS_ASSERT access type 2020-03-21 09:42:50 +01:00
Makefile kcsan, ubsan: Make KCSAN+UBSAN work together 2020-01-07 07:47:23 -08:00
report.c kcsan: Fix misreporting if concurrent races on same address 2020-03-21 09:43:41 +01:00
test.c kcsan: Fix 0-sized checks 2020-03-21 09:42:42 +01:00