diff options
| author | Marco Elver <elver@google.com> | 2021-08-09 13:25:11 +0200 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@kernel.org> | 2021-09-13 16:41:19 -0700 |
| commit | ade3a58b2d40555701143930ead3d44d0b52ca9e (patch) | |
| tree | cf682459e524acd2803d907d4473e23ab6f57db5 /lib/test_fortify/write_overflow-strncpy.c | |
| parent | 80804284103ab95e1fe92f167af690ef4c9a6560 (diff) | |
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>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy.c')
0 files changed, 0 insertions, 0 deletions