Documentation/dev-tools/kcsan.rst

4 The Kernel Concurrency Sanitizer (KCSAN) is a dynamic race detector, which
24 A typical data race report looks like this::
27     BUG: KCSAN: data-race in generic_permission / kernfs_refresh_inode
62 the race. It is followed by the access types and stack traces of the 2 threads
63 involved in the data race.
65 The other less common type of data race report looks like this::
68     BUG: KCSAN: data-race in e1000_clean_rx_irq+0x551/0xb10
70     race at unknown origin, with read to 0xffff933db8a2ae6c of 1 bytes by interrupt on cpu 0:
92 racing thread, but a race was inferred due to the data value of the watched
100 It may be desirable to disable data race detection for specific accesses,
106   behaviour when encountering a data race is deemed safe.
108 * Disabling data race detection for entire functions can be accomplished by
118 * To disable data race detection for a particular compilation unit, add to the
123 * To disable data race detection for all compilation units listed in a
134   observed to remain unchanged, do not report the data race.
173   overall system performance and race detection ability.
177   Larger values result in the window in which we may observe a race to
190 In an execution, two memory accesses form a *data race* if they *conflict*,
209 assumes that as long as a plain access is not observed to race with another
216 architecture) leads to an observable data race (e.g. entering a critical
217 section erroneously), KCSAN would report the resulting data race.
222 For code with complex concurrency design, race-condition bugs may not always
262    after delay; if the values mismatch, we infer a race of unknown origin.
303 An alternative data race detection approach for the kernel can be found in the
305 KTSAN is a happens-before data race detector, which explicitly establishes the