Searched refs:deadlock (Results 1 – 25 of 62) sorted by relevance
123
| /Linux-v4.19/Documentation/aoe/ |
| D | todo.txt | 1 There is a potential for deadlock when allocating a struct sk_buff for
4 there are no other pages available, then deadlock may occur when a
7 deadlock under memory pressure.
14 deadlock.
|
| /Linux-v4.19/arch/ia64/sn/kernel/sn2/ |
| D | sn2_smp.c | 175 int active, max_active, deadlock, flush_opt = sn2_flush_opt; in sn2_global_tlb_purge() local
270 deadlock = 0; in sn2_global_tlb_purge()
287 if ((deadlock = wait_piowc())) { in sn2_global_tlb_purge()
315 if (flush_opt == 1 && deadlock) { in sn2_global_tlb_purge()
|
| /Linux-v4.19/drivers/gpu/drm/i915/ |
| D | intel_hangcheck.c | 132 engine->hangcheck.deadlock++; in semaphore_passed()
142 if (signaller->hangcheck.deadlock >= I915_NUM_ENGINES) in semaphore_passed()
162 engine->hangcheck.deadlock = 0; in semaphore_clear_deadlocks()
|
| /Linux-v4.19/Documentation/locking/ |
| D | ww-mutex-design.txt | 19 makes. Which results in the potential for deadlock. The problem gets
29 from a global counter. In case of deadlock while locking all the buffers
36 and the deadlock handling approach is called Wait-Die. The name is based on
85 no deadlock potential and hence the ww_mutex_lock call will block and not
103 better to avoid grabbing a deadlock avoidance ticket).
323 Method 4: Only lock one single objects. In that case deadlock detection and
325 produce a deadlock within just one class. To simplify this case the w/w mutex
345 contention for a new lock and hence a true chance of deadlock. In that
|
| D | 00-INDEX | 16 - Intro to Mutex wait/would deadlock handling.s
|
| D | lockdep-design.txt | 102 thus could result in a lock inversion deadlock. Likewise, a softirq-safe
127 could lead to a lock inversion deadlock - even if that lock scenario did
227 lock related deadlock. [*]
230 occur in practice to prove a deadlock: only the simple 'component'
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | directory-locking | 56 If no directory is its own ancestor, the scheme above is deadlock-free.
80 Now consider the minimal deadlock. Each process is blocked on
91 Thus link creation can't be a part of deadlock - it can't be
112 Contradiction. I.e. deadlock is impossible. Q.E.D.
|
| D | fuse.txt | 198 c) Accidental deadlock
200 d) Malicious deadlock
360 There are a couple of ways in which to deadlock a FUSE filesystem.
364 Scenario 1 - Simple deadlock
382 Scenario 2 - Tricky deadlock
|
| D | locks.txt | 46 race and deadlock conditions that the current solution was the only
|
| D | index.rst | 221 deadlock. The first thing to note is that each task can only have a
239 behaviour to :c:func:`jbd2_journal_start` so you can deadlock here just as
|
| /Linux-v4.19/Documentation/arm/ |
| D | swp_emulation | 25 cause programs that perform SWP operations to uncached memory to deadlock, as
|
| /Linux-v4.19/tools/memory-model/ |
| D | lock.cat | 56 * inside a critical section (for the same lock) always deadlock.
78 (* Allow up to one unmatched LKW per location; more must deadlock *)
|
| /Linux-v4.19/Documentation/RCU/ |
| D | UP.txt | 58 be self-deadlock.
120 self-deadlock.
|
| D | whatisRCU.txt | 569 you allow nested rcu_read_lock() calls, you can deadlock.
625 from deadlock (an important property of RCU). The reason for this is
628 so there can be no deadlock cycle.
630 Quick Quiz #1: Why is this argument naive? How could a deadlock
632 kernel? How could this deadlock be avoided?
659 participate in a deadlock cycle!
957 Quick Quiz #1: Why is this argument naive? How could a deadlock
979 One way to avoid this deadlock is to use an approach like
984 release rcu_gp_mutex, avoiding the deadlock.
986 Even in the absence of deadlock, this RCU implementation
|
| D | rcu.txt | 25 acquire locks can also greatly simplify deadlock-avoidance code.
|
| /Linux-v4.19/Documentation/networking/ |
| D | driver.txt | 72 This error can deadlock sockets waiting for send buffer room
|
| D | spider_net.txt | 131 deadlock condition, as the tail pointer will be pointing at this descr,
135 is a potential deadlock, with the OS waiting for one descr to fill,
|
| /Linux-v4.19/Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 17 The traditional way to avoid this deadlock problem is to clear __GFP_FS
|
| /Linux-v4.19/Documentation/i2c/ |
| D | i2c-topology | 148 __i2c_transfer), or a deadlock will follow. There are a couple of
186 that they do not deadlock the root adapter.
188 unlocked i2c-transfer, so that it does not deadlock the parent
|
| /Linux-v4.19/Documentation/x86/x86_64/ |
| D | machinecheck | 55 deadlock. Higher tolerant values trade potentially better uptime
|
| /Linux-v4.19/Documentation/infiniband/ |
| D | core_locking.txt | 104 semaphores that could cause deadlock if a consumer calls back into
|
| /Linux-v4.19/Documentation/device-mapper/ |
| D | dm-raid.txt | 346 1.12.1 Fix for MD deadlock between mddev_suspend() and md_write_start() available
348 1.13.1 Fix deadlock caused by early md_stop_writes(). Also fix size an
352 deadlock/potential data corruption. Update superblock when
|
| /Linux-v4.19/arch/arm/ |
| D | Kconfig | 977 bool "ARM errata: Processor deadlock when a false hazard is created"
985 hazard might then cause a processor deadlock. The workaround enables
1128 bool "ARM errata: A data cache maintenance operation which aborts, might lead to deadlock"
1134 to deadlock. This workaround puts DSB before executing ISB if
1157 bool "ARM errata: A12: some seqs of opposed cond code instrs => deadlock or corruption"
1162 instruction might deadlock. Fixed in r0p1.
1164 lead to either a data corruption or a CPU deadlock. Not fixed in
1178 deadlock when the VMOV instructions are issued out-of-order.
1181 bool "ARM errata: A12: DMB NSHST/ISHST mixed ... might cause deadlock"
1187 and Device/Strongly-Ordered loads and stores might cause deadlock
[all …]
|
| /Linux-v4.19/arch/arm/mach-omap2/ |
| D | Kconfig | 245 system to deadlock.
|
| /Linux-v4.19/arch/arm64/ |
| D | Kconfig | 312 …bool "Cortex-A53: 826319: System might deadlock if a write cannot complete until read data is acce…
322 system can deadlock.
397 bool "Cortex-A57: 832075: possible deadlock on mixing exclusive memory accesses with device loads"
403 Affected Cortex-A57 parts might deadlock when exclusive load/store
971 with SWP emulation enabled, leading to deadlock of the user
978 perform SWP operations to uncached memory to deadlock.
|
123
