Home
last modified time | relevance | path

Searched full:deadlock (Results 1 – 25 of 702) sorted by relevance

12345678910>>...29

/Linux-v6.6/Documentation/locking/
Dlockdep-design.rst129 deadlock may happen. For example, in the scenario that after this lock
131 lock will be attempted to acquire twice, which creates a deadlock,
132 referred to as lock recursion deadlock.
148 because this could lead to a deadlock - referred to as lock inversion
149 deadlock - as attempts to acquire the two locks form a circle which
164 thus could result in a lock inversion deadlock. Likewise, a softirq-safe
189 could lead to a lock inversion deadlock - even if that lock scenario did
289 lock related deadlock. [1]_
292 occur in practice to prove a deadlock: only the simple 'component'
402 to deadlock possibility.
[all …]
Dww-mutex-design.rst2 Wound/Wait Deadlock-Proof Mutex Design
20 makes. Which results in the potential for deadlock. The problem gets
30 from a global counter. In case of deadlock while locking all the buffers
37 and the deadlock handling approach is called Wait-Die. The name is based on
86 no deadlock potential and hence the ww_mutex_lock call will block and not
105 better to avoid grabbing a deadlock avoidance ticket).
327 Method 4: Only lock one single objects. In that case deadlock detection and
329 produce a deadlock within just one class. To simplify this case the w/w mutex
352 contention for a new lock and hence a true chance of deadlock. In that
/Linux-v6.6/Documentation/admin-guide/aoe/
Dtodo.rst4 There is a potential for deadlock when allocating a struct sk_buff for
7 there are no other pages available, then deadlock may occur when a
10 deadlock under memory pressure.
17 deadlock.
/Linux-v6.6/kernel/locking/
Drtmutex.c556 * Deadlock detection is conditional:
558 * If CONFIG_DEBUG_RT_MUTEXES=n, deadlock detection is only conducted
561 * If CONFIG_DEBUG_RT_MUTEXES=y, deadlock detection is always
565 * deadlock detection is disabled independent of the detect argument
583 * Adjust the priority chain. Also used for deadlock detection.
588 * @chwalk: do we have to carry out deadlock detection?
761 * Even when we start with ww_mutex we can disable deadlock detection, in rt_mutex_adjust_prio_chain()
762 * since we would supress a ww_mutex induced deadlock at [6] anyway. in rt_mutex_adjust_prio_chain()
766 * NOTE: if someone were to create a deadlock between 2 ww_classes we'd in rt_mutex_adjust_prio_chain()
781 * If deadlock detection is off, we stop here if we in rt_mutex_adjust_prio_chain()
[all …]
/Linux-v6.6/Documentation/filesystems/
Ddirectory-locking.rst66 If no directory is its own ancestor, the scheme above is deadlock-free.
92 Now consider the minimal deadlock. Each process is blocked on
103 Thus link creation can't be a part of deadlock - it can't be
124 Contradiction. I.e. deadlock is impossible. Q.E.D.
Dfuse.rst184 c) Accidental deadlock
186 d) Malicious deadlock
364 There are a couple of ways in which to deadlock a FUSE filesystem.
368 **Scenario 1 - Simple deadlock**::
381 | | *DEADLOCK*
385 **Scenario 2 - Tricky deadlock**
414 | | * DEADLOCK *
/Linux-v6.6/Documentation/RCU/
DUP.rst56 Example 3: Death by Deadlock
62 be self-deadlock *even if* this invocation occurred from a later
95 the deadlock-avoidance benefits called out above.
137 self-deadlock.
/Linux-v6.6/lib/
Dlocking-selftest.c298 * AA deadlock:
422 * detecting a read-lock/lock-write deadlock: if the chain cache doesn't differ
431 * { Not a deadlock, B -> A is added in the chain cache }
437 * { B->A found in chain cache, not reported as a deadlock }
524 * ABBA deadlock:
556 * AB BC CA deadlock:
589 * AB CA BC deadlock:
622 * AB BC CD DA deadlock:
656 * AB CD BD DA deadlock:
689 * AB CD BC DA deadlock:
[all …]
/Linux-v6.6/drivers/gpu/drm/nouveau/
Dnouveau_backlight.c166 goto deadlock; in nv50_edp_get_brightness()
176 goto deadlock; in nv50_edp_get_brightness()
188 deadlock: in nv50_edp_get_brightness()
209 goto deadlock; in nv50_edp_set_brightness()
219 goto deadlock; in nv50_edp_set_brightness()
230 deadlock: in nv50_edp_set_brightness()
/Linux-v6.6/scripts/coccinelle/api/
Dstream_open.cocci6 // its read and write. Rationale for the conversion is to avoid deadlock in
232 …"ERROR: %s: .read() can deadlock .write(); change nonseekable_open -> stream_open to fix." % (fops…
248 + nonseekable_open /* read & write (was deadlock) */
259 + nonseekable_open /* read & write (no direct deadlock) */
/Linux-v6.6/fs/ocfs2/dlm/
Ddlmapi.h48 DLM_DEADLOCK, /* 30: deadlock recovery refused this request */
123 #define LKM_NODLCKWT 0x00000800 /* this lock wont deadlock (U) */
130 #define LKM_SNGLDLCK 0x00040000 /* request can self-deadlock (U) */
133 #define LKM_XID 0x00200000 /* use transaction id for deadlock (U) */
/Linux-v6.6/tools/memory-model/scripts/
Djudgelitmus.sh116 if test "$outcome" = DEADLOCK
131 echo " !!! Unexpected non-$outcome deadlock" $litmus
134 echo " !!! Unexpected non-$outcome deadlock" $litmus >> $LKMM_DESTDIR/$litmusout 2>&1
Dcheckghlitmus.sh39 xargs -r grep -E -l '^ \* Result: (Never|Sometimes|Always|DEADLOCK)' |
45 xargs < $T/list-C -r grep -E -l '^ \* Result: (Never|Sometimes|Always|DEADLOCK)' > $T/list-C-result
/Linux-v6.6/tools/testing/selftests/timers/
Dleapcrash.c1 /* Demo leapsecond deadlock
7 * This test demonstrates leapsecond deadlock that is possible
/Linux-v6.6/include/drm/
Ddrm_modeset_lock.h165 * forth between the labels on deadlock and error conditions.
194 * deadlock conditions are properly handled.
199 * there is a deadlock or other failure with acquire or backoff, ret will be set
/Linux-v6.6/tools/testing/selftests/bpf/progs/
Dtimer.c189 /* try to cancel ourself. It shouldn't deadlock. */ in timer_cb2()
194 * It shouldn't deadlock either. in timer_cb2()
210 /* try to cancel ourself. It shouldn't deadlock. */ in timer_cb2()
215 * It shouldn't deadlock either. in timer_cb2()
/Linux-v6.6/arch/arm/
DKconfig651 bool "ARM errata: Processor deadlock when a false hazard is created"
659 hazard might then cause a processor deadlock. The workaround enables
829 bool "ARM errata: A data cache maintenance operation which aborts, might lead to deadlock"
835 to deadlock. This workaround puts DSB before executing ISB if
858 bool "ARM errata: A12: some seqs of opposed cond code instrs => deadlock or corruption"
863 instruction might deadlock. Fixed in r0p1.
865 lead to either a data corruption or a CPU deadlock. Not fixed in
879 deadlock when the VMOV instructions are issued out-of-order.
882 bool "ARM errata: A12: DMB NSHST/ISHST mixed ... might cause deadlock"
888 and Device/Strongly-Ordered loads and stores might cause deadlock
[all …]
/Linux-v6.6/include/uapi/linux/
Ddlm.h44 * it was first demoted to NL to avoid conversion deadlock.
54 * -EDEADLK if a deadlock was detected
/Linux-v6.6/drivers/pci/hotplug/
Dpciehp_pci.c69 * to avoid AB-BA deadlock with device_lock. in pciehp_configure_device()
117 * to avoid AB-BA deadlock with device_lock. in pciehp_unconfigure_device()
/Linux-v6.6/arch/microblaze/mm/
Dfault.c131 * we will deadlock attempting to validate the fault against the in do_page_fault()
137 * the source reference check when there is a possibility of a deadlock. in do_page_fault()
140 * thus avoiding the deadlock. in do_page_fault()
/Linux-v6.6/include/linux/
Dshrinker.h48 * is below shrinkable limit). No deadlock checks should be done during the
51 * deadlock condition is no longer pending.
/Linux-v6.6/drivers/net/ethernet/chelsio/cxgb/
Dtp.c14 /* Pause deadlock avoidance parameters */
42 * Enable pause frame deadlock prevention. in tp_init()
/Linux-v6.6/tools/arch/powerpc/include/uapi/asm/
Derrno.h9 #define EDEADLOCK 58 /* File locking deadlock error */
/Linux-v6.6/arch/powerpc/include/uapi/asm/
Derrno.h9 #define EDEADLOCK 58 /* File locking deadlock error */
/Linux-v6.6/drivers/gpu/drm/amd/amdgpu/
Damdgpu_mes.h420 * recursively reenter the reclaim code and cause a deadlock. The
425 * scenario of a deadlock:
430 * In this scenario Thread B gets involved in a deadlock even without

12345678910>>...29