| /linux/tools/memory-model/ |
| H A D | linux-kernel.cat | 212 let pre-race = ext & ((Plain * M) | ((M \ IW) * Plain))
215 let wr-incoh = pre-race & rf & rw-xbstar^-1
216 let rw-incoh = pre-race & fr & wr-vis^-1
217 let ww-incoh = pre-race & co & ww-vis^-1
222 let ww-race = (pre-race & co) \ ww-nonrace
223 let wr-race = (pre-race & (co? ; rf)) \ wr-vis \ rw-xbstar^-1
224 let rw-race = (pre-race
[all...] |
| /linux/Documentation/translations/zh_CN/dev-tools/ |
| H A D | kcsan.rst | 33 BUG: KCSAN: data-race in test_kernel_read / test_kernel_write
61 BUG: KCSAN: data-race in test_kernel_rmw_array+0x71/0xd0
63 race at unknown origin, with read to 0xffffffffc009bdb0 of 8 bytes by task 515 on cpu 2:
260 x = 1; // data race!
266 ... = x; // data race!
|
| /linux/Documentation/driver-api/firmware/ |
| H A 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.
|
| H A D | firmware_cache.rst | 21 filesystem to mount or dealing with possible race issues with lookups as the
|
| /linux/tools/memory-model/Documentation/ |
| H A D | access-marking.txt | 20 2. Data-race marking, for example, "data_race(a = b);"
43 Therefore, if a given access is involved in an intentional data race,
52 race with one of data_race(), READ_ONCE(), or WRITE_ONCE(), will prevent
104 that the resulting data race was intentional.
114 in a retry. Unless the race condition that resulted in the bogus value
128 that the resulting data race was intentional.
149 that the resulting data race was intentional.
165 because KCSAN will have no way of knowing that the resulting data race
543 When designing stress tests it is important to ensure that race conditions
617 [1] "Concurrency bugs should fear the big bad data-race detector (part 2)"
|
| H A 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/tools/testing/selftests/proc/ |
| H A D | .gitignore | 8 /proc-maps-race
|
| H A D | Makefile | 12 TEST_GEN_PROGS += proc-maps-race
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | uprobe_syscall.c | 653 static USDT_DEFINE_SEMA(race);
674 __stringify(USDT_SEMA(race)), in worker_attach()
753 ASSERT_FALSE(USDT_SEMA_IS_ACTIVE(race), "race_semaphore"); in test_uprobe_race()
|
| H A D | timer.c | 49 prog_fd = bpf_program__fd(timer_skel->progs.race); in timer()
|
| /linux/net/netfilter/ |
| H A D | xt_hashlimit.c | 217 const struct dsthash_dst *dst, bool *race) in dsthash_alloc_init() argument
229 *race = true; in dsthash_alloc_init()
734 bool race = false; in hashlimit_mt_common() local
743 dh = dsthash_alloc_init(hinfo, &dst, &race); in hashlimit_mt_common()
747 } else if (race) { in hashlimit_mt_common()
|
| /linux/Documentation/driver-api/soundwire/ |
| H A D | locking.rst | 6 following locks in order to avoid race conditions in Bus operations on
|
| /linux/Documentation/input/devices/ |
| H A D | bcm5974.rst | 43 different interfaces of the same usb device. This creates a race condition
|
| /linux/Documentation/filesystems/ |
| H A D | locks.rst | 50 race and deadlock conditions that the current solution was the only
|
| /linux/Documentation/arch/arm/ |
| H A 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/Documentation/misc-devices/ |
| H A D | amd-sbi.rst | 29 among protocols as transactions may create race condition.
|
| /linux/Documentation/process/ |
| H A D | code-of-conduct.rst | 14 personal appearance, race, religion, or sexual identity and orientation.
|
| /linux/Documentation/networking/ |
| H A D | driver.rst | 70 /* This should be a very rare race - log it. */
|
| H A D | page_pool.rst | 56 a page will cause no race conditions is enough.
|
| /linux/Documentation/scsi/ |
| H A D | ChangeLog.ips | 105 0.99.04 - Fix race condition in the passthru mechanism
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | timer.c | 493 int race(void *ctx)
403 int race(void *ctx) race() function
|
| /linux/Documentation/driver-api/media/ |
| H A D | dtv-demux.rst | 38 possibilities of lost update and race condition problems should be
|
| /linux/Documentation/locking/ |
| H A D | robust-futexes.rst | 62 - it has quite complex locking and race scenarios. The vma-based
108 There is one race possible though: since adding to and removing from the
|
| /linux/Documentation/arch/riscv/ |
| H A D | cmodx.rst | 24 without a race condition. This series makes atmoic code patching possible in
|
| /linux/Documentation/gpu/ |
| H A D | drm-vm-bind-locking.rst | 231 new exec function may not race with the eviction.
556 * The unmapping and mapping of a gpu_vma must not race.
566 is held in read mode during mapping, it will not race with the
570 object, will similarly ensure we are race-free.
|