Marco Elver ade3a58b2d kcsan: test: Fix flaky test case ... If CONFIG_KCSAN_REPORT_VALUE_CHANGE_ONLY=n, then we may also see data races between the writers only. If we get unlucky and never capture a read-write data race, but only the write-write data races, then the test_no_value_change* test cases may incorrectly fail. The second problem is that the initial value needs to be reset, as otherwise we might actually observe a value change at the start. Fix it by also looking for the write-write data races, and resetting the value to what will be written. Signed-off-by: Marco Elver <elver@google.com> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>		2021-09-13 16:41:19 -07:00
..
core.c	kcsan: Print if strict or non-strict during init	2021-07-20 13:49:44 -07:00
debugfs.c	kcsan: use u64 instead of cycles_t	2021-07-30 17:09:02 +02:00
encoding.h	kcsan: Add missing license and copyright headers	2021-03-08 14:27:43 -08:00
kcsan.h	kcsan: Report observed value changes	2021-05-18 10:58:15 -07:00
kcsan_test.c	kcsan: test: Fix flaky test case	2021-09-13 16:41:19 -07:00
Makefile	kcsan: Make test follow KUnit style recommendations	2021-03-08 14:27:43 -08:00
permissive.h	kcsan: permissive: Ignore data-racy 1-bit value changes	2021-07-20 13:49:44 -07:00
report.c	Merge branch 'kcsan.2021.05.18a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu	2021-07-04 12:29:16 -07:00
selftest.c	kcsan: Add missing license and copyright headers	2021-03-08 14:27:43 -08:00