/Linux-v6.6/Documentation/dev-tools/ |
D | kcsan.rst | 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, [all …]
|
/Linux-v6.6/tools/memory-model/ |
D | linux-kernel.cat | 202 let pre-race = ext & ((Plain * M) | ((M \ IW) * Plain)) 205 let wr-incoh = pre-race & rf & rw-xbstar^-1 206 let rw-incoh = pre-race & fr & wr-vis^-1 207 let ww-incoh = pre-race & co & ww-vis^-1 212 let ww-race = (pre-race & co) \ ww-nonrace 213 let wr-race = (pre-race & (co? ; rf)) \ wr-vis \ rw-xbstar^-1 214 let rw-race = (pre-race & fr) \ rw-xbstar 216 flag ~empty (ww-race | wr-race | rw-race) as data-race
|
/Linux-v6.6/lib/ |
D | Kconfig.kcsan | 14 bool "KCSAN: dynamic data race detector" 21 data-race detector that relies on compile-time instrumentation. 51 external functions on report generation; if a race report is 70 various race scenarios, and verifies the reports generated to 131 results in more aggressive race detection, whereas a larger value 155 int "Duration in milliseconds, in which any given race is only reported once" 158 Any given race is only reported once in the defined time window. 173 conflicting access is of unknown origin. This type of race is 174 reported if it was only possible to infer a race due to a data value 178 bool "Strict data-race checking" [all …]
|
/Linux-v6.6/Documentation/driver-api/firmware/ |
D | direct-fs-lookup.rst | 22 a race is possible with loading the driver and the real rootfs not yet being 23 available. Stuffing the firmware into initramfs resolves this race issue, 24 however note that using initrd does not suffice to address the same race.
|
D | firmware_cache.rst | 21 filesystem to mount or dealing with possible race issues with lookups as the
|
/Linux-v6.6/tools/testing/selftests/kvm/x86_64/ |
D | recalc_apic_map_test.c | 21 static void *race(void *arg) in race() function 60 TEST_ASSERT_EQ(pthread_create(&thread, NULL, race, vcpus[0]), 0); in main()
|
/Linux-v6.6/drivers/gpu/drm/ci/xfails/ |
D | rockchip-rk3399-flakes.txt | 3 kms_flip@dpms-vs-vblank-race-interruptible 5 kms_flip@modeset-vs-vblank-race-interruptible
|
D | msm-sdm845-flakes.txt | 11 kms_flip@dpms-vs-vblank-race-interruptible
|
D | rockchip-rk3399-fails.txt | 6 kms_flip@dpms-vs-vblank-race,Fail
|
/Linux-v6.6/tools/perf/tests/attr/ |
D | system-wide-dummy | 1 # Event added by system-wide or CPU perf-record to handle the race of
|
/Linux-v6.6/tools/memory-model/Documentation/ |
D | access-marking.txt | 19 2. Data-race marking, for example, "data_race(a = b);" 37 Therefore, if a given access is involved in an intentional data race, 46 race with one of data_race(), READ_ONCE(), or WRITE_ONCE(), will prevent 98 that the resulting data race was intentional. 108 in a retry. Unless the race condition that resulted in the bogus value 122 that the resulting data race was intentional. 143 that the resulting data race was intentional. 159 because KCSAN will have no way of knowing that the resulting data race 520 When designing stress tests it is important to ensure that race conditions 594 [1] "Concurrency bugs should fear the big bad data-race detector (part 2)"
|
D | explanation.txt | 2231 program executes, there will not be any data races. A "data race" 2247 are "race candidates" if they satisfy 1 - 4. Thus, whether or not two 2248 race candidates actually do race in a given execution depends on 2251 The LKMM tries to determine whether a program contains race candidates 2253 a potential data race and makes no predictions about the program's 2256 Determining whether two accesses are race candidates is easy; you can 2366 limitations. For one, it is not allowed to introduce a data race into 2368 race (if it could, memory models would be useless and no multithreaded 2423 This program does not contain a data race. Although the U and V 2424 accesses are race candidates, the LKMM can prove they are not [all …]
|
/Linux-v6.6/Documentation/arch/arm/ |
D | index.rst | 12 cluster-pm-race-avoidance
|
D | cluster-pm-race-avoidance.rst | 2 Cluster-wide Power-up/power-down race avoidance algorithm 187 race avoidance algorithm. 271 The race avoidance algorithm does not provide a way to determine 452 The race avoidance algorithm documented above does not provide a
|
/Linux-v6.6/Documentation/filesystems/ |
D | hpfs.rst | 239 Fixed a race-condition when write_inode is called while deleting file 243 Rewritten locking to avoid race-conditions 296 Fixed a possible bitmap race 302 Fixed a nondestructive race in rename 325 Fixed race-condition in buffer code - it is in all filesystems in Linux; 332 Fixed non-crashing race in unlink (Alexander Viro)
|
D | locks.rst | 50 race and deadlock conditions that the current solution was the only
|
/Linux-v6.6/tools/testing/selftests/media_tests/ |
D | regression_test.txt | 32 Regression test for media_devnode unregister race with ioctl_syscall:
|
/Linux-v6.6/Documentation/driver-api/soundwire/ |
D | locking.rst | 6 following locks in order to avoid race conditions in Bus operations on
|
/Linux-v6.6/net/netfilter/ |
D | xt_hashlimit.c | 218 const struct dsthash_dst *dst, bool *race) in dsthash_alloc_init() argument 230 *race = true; in dsthash_alloc_init() 732 bool race = false; in hashlimit_mt_common() local 741 dh = dsthash_alloc_init(hinfo, &dst, &race); in hashlimit_mt_common() 745 } else if (race) { in hashlimit_mt_common()
|
/Linux-v6.6/Documentation/hwmon/ |
D | asus_ec_sensors.rst | 55 Sensor values are read from EC registers, and to avoid race with the board
|
/Linux-v6.6/Documentation/power/ |
D | suspend-and-cpuhotplug.rst | 21 What happens when regular CPU hotplug and Suspend-to-RAM race with each other 259 Are there any known problems when regular CPU hotplug and suspend race 272 2. If a regular CPU hotplug stress test happens to race with the freezer due
|
/Linux-v6.6/Documentation/input/devices/ |
D | bcm5974.rst | 43 different interfaces of the same usb device. This creates a race condition
|
/Linux-v6.6/Documentation/networking/ |
D | driver.rst | 70 /* This should be a very rare race - log it. */
|
/Linux-v6.6/Documentation/process/ |
D | code-of-conduct.rst | 14 personal appearance, race, religion, or sexual identity and orientation.
|
/Linux-v6.6/Documentation/scsi/ |
D | ChangeLog.ips | 105 0.99.04 - Fix race condition in the passthru mechanism
|