diff options
| author | Marco Elver <elver@google.com> | 2021-10-20 10:57:49 +0200 |
|---|---|---|
| committer | Marco Elver <me@marcoelver.com> | 2021-10-20 11:44:15 +0200 |
| commit | 418a00eb23ef6f6d2f60255c6185520ceaa2d0db (patch) | |
| tree | e15ea6387d2c5237ec5126e7eeafaddc16c0f8e4 /dashboard/config/linux/bits | |
| parent | b541beac5b929237d926ac9a616aad960822744a (diff) | |
dashboard/config/linux: kcsan: do not pretend writes are atomic
Do not pretend writes are atomic. While this may currently be a
prevailing preference in the community, it does hide more interesting
bugs [1].
Since we moderate data races anyway, and are still drowning in data
races, a few more won't hurt.
What it does help with, however, is getting better signals about harmful
data races. Most of the read/write data races provide weak signals, but
write/write data races should provide a stronger harmfulness signal [1],
which will help us in selecting data races to investigate further.
[1] https://googleprojectzero.blogspot.com/2021/10/how-simple-linux-kernel-memory.html
Diffstat (limited to 'dashboard/config/linux/bits')
| -rw-r--r-- | dashboard/config/linux/bits/kcsan.yml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/dashboard/config/linux/bits/kcsan.yml b/dashboard/config/linux/bits/kcsan.yml index 6f7670c0d..7a8dea258 100644 --- a/dashboard/config/linux/bits/kcsan.yml +++ b/dashboard/config/linux/bits/kcsan.yml @@ -13,6 +13,6 @@ config: - KCSAN_SKIP_WATCH_RANDOMIZE - KCSAN_REPORT_RACE_UNKNOWN_ORIGIN: n - KCSAN_REPORT_VALUE_CHANGE_ONLY - - KCSAN_ASSUME_PLAIN_WRITES_ATOMIC + - KCSAN_ASSUME_PLAIN_WRITES_ATOMIC: n - KCSAN_IGNORE_ATOMICS - KCSAN_PERMISSIVE: [v5.14] # TODO: change to 5.15 once released |