Lines Matching refs:race

7 The Kernel Concurrency Sanitizer (KCSAN) is a dynamic race detector, which
27 A typical data race report looks like this::
30     BUG: KCSAN: data-race in test_kernel_read / test_kernel_write
52 the race. It is followed by the access types and stack traces of the 2 threads
53 involved in the data race. If KCSAN also observed a value change, the observed
56 The other less common type of data race report looks like this::
59     BUG: KCSAN: data-race in test_kernel_rmw_array+0x71/0xd0
61     race at unknown origin, with read to 0xffffffffc009bdb0 of 8 bytes by task 515 on cpu 2:
75 racing thread, but a race was inferred due to the data value of the watched
85 It may be desirable to disable data race detection for specific accesses,
91   behaviour when encountering a data race is deemed safe.  Please see
94 * Disabling data race detection for entire functions can be accomplished by
104 * To disable data race detection for a particular compilation unit, add to the
109 * To disable data race detection for all compilation units listed in a
122   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*,
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.
292         x = 1;                  // data race!
298         ... = x;                    // data race!
304 ``flag``, a data race is detected. With the correct barriers in place, ``x``
306 and no data race would be detected.
353 An alternative data race detection approach for the kernel can be found in the
355 KTSAN is a happens-before data race detector, which explicitly establishes the