Home
last modified time | relevance | path

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

12345678910>>...26

/linux/Documentation/locking/
H A 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 …]
H A 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/Documentation/admin-guide/aoe/
H A 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/Documentation/filesystems/
H A Ddirectory-locking.rst130 Deadlock avoidance
133 If no directory is its own ancestor, the scheme above is deadlock-free.
168 contended locks in the minimal deadlock will be of the same rank,
196 so they would all hold simultaneously at the deadlock time and
207 D1,...,Dn all hold simultaneously at the deadlock time. Moreover,
237 properties required for a minimal deadlock can not exist.
240 rename is crucial - without it a deadlock would be possible. Indeed,
248 the locks) and voila - we have a deadlock.
H A 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/kernel/locking/
H A Drtmutex.c578 * Deadlock detection is conditional:
580 * If CONFIG_DEBUG_RT_MUTEXES=n, deadlock detection is only conducted
583 * If CONFIG_DEBUG_RT_MUTEXES=y, deadlock detection is always
587 * deadlock detection is disabled independent of the detect argument
605 * Adjust the priority chain. Also used for deadlock detection.
610 * @chwalk: do we have to carry out deadlock detection?
783 * Even when we start with ww_mutex we can disable deadlock detection, in rt_mutex_adjust_prio_chain()
784 * since we would supress a ww_mutex induced deadlock at [6] anyway. in rt_mutex_adjust_prio_chain()
788 * NOTE: if someone were to create a deadlock between 2 ww_classes we'd in rt_mutex_adjust_prio_chain()
803 * If deadlock detection is off, we stop here if we in rt_mutex_adjust_prio_chain()
[all …]
/linux/drivers/gpu/drm/nouveau/
H A Dnouveau_backlight.c130 goto deadlock; in nv50_edp_get_brightness()
140 goto deadlock; in nv50_edp_get_brightness()
152 deadlock: in nv50_edp_get_brightness()
173 goto deadlock; in nv50_edp_set_brightness()
183 goto deadlock; in nv50_edp_set_brightness()
194 deadlock: in nv50_edp_set_brightness()
/linux/lib/
H A 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/Documentation/RCU/
H A 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.
H A DwhatisRCU.rst656 you allow nested rcu_read_lock() calls, you can deadlock.
712 from deadlock (an important property of RCU). The reason for this is
715 so there can be no deadlock cycle.
720 Why is this argument naive? How could a deadlock
722 kernel? How could this deadlock be avoided?
751 participate in a deadlock cycle!
1204 Why is this argument naive? How could a deadlock
1227 One way to avoid this deadlock is to use an approach like
1232 release rcu_gp_mutex, avoiding the deadlock.
1234 Even in the absence of deadlock, this RCU implementation
/linux/fs/ocfs2/dlm/
H A Ddlmapi.h48 DLM_DEADLOCK, /* 30: deadlock recovery refused this request */
121 #define LKM_NODLCKWT 0x00000800 /* this lock wont deadlock (U) */
128 #define LKM_SNGLDLCK 0x00040000 /* request can self-deadlock (U) */
131 #define LKM_XID 0x00200000 /* use transaction id for deadlock (U) */
/linux/scripts/coccinelle/api/
H A Dstream_open.cocci6 // its read and write. Rationale for the conversion is to avoid deadlock in
231 …"ERROR: %s: .read() can deadlock .write(); change nonseekable_open -> stream_open to fix." % (fops…
247 + nonseekable_open /* read & write (was deadlock) */
258 + nonseekable_open /* read & write (no direct deadlock) */
/linux/tools/memory-model/scripts/
H A 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
H A 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/fs/bcachefs/
H A Dsix.h99 * ordering is required to prevent deadlock, object reuse may change the
100 * correct lock order for that object and cause a deadlock. should_sleep_fn
102 * this deadlock.
109 * implement full cycle detection for deadlock avoidance.
112 * graph of held locks to check for a deadlock. The upper layer must track
/linux/arch/arm/
H A DKconfig572 bool "ARM errata: Processor deadlock when a false hazard is created"
580 hazard might then cause a processor deadlock. The workaround enables
750 bool "ARM errata: A data cache maintenance operation which aborts, might lead to deadlock"
756 to deadlock. This workaround puts DSB before executing ISB if
779 bool "ARM errata: A12: some seqs of opposed cond code instrs => deadlock or corruption"
784 instruction might deadlock. Fixed in r0p1.
786 lead to either a data corruption or a CPU deadlock. Not fixed in
800 deadlock when the VMOV instructions are issued out-of-order.
803 bool "ARM errata: A12: DMB NSHST/ISHST mixed ... might cause deadlock"
809 and Device/Strongly-Ordered loads and stores might cause deadlock
[all …]
/linux/include/drm/
H A 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/tools/testing/selftests/timers/
H A Dleapcrash.c1 /* Demo leapsecond deadlock
7 * This test demonstrates leapsecond deadlock that is possible
/linux/tools/testing/selftests/bpf/progs/
H A Dtimer.c193 /* try to cancel ourself. It shouldn't deadlock. */ in timer_cb2()
198 * It shouldn't deadlock either. in timer_cb2()
214 /* try to cancel ourself. It shouldn't deadlock. */ in timer_cb2()
219 * It shouldn't deadlock either. in timer_cb2()
/linux/include/uapi/linux/
H A Ddlm.h44 * it was first demoted to NL to avoid conversion deadlock.
54 * -EDEADLK if a deadlock was detected
/linux/drivers/pci/hotplug/
H A Dpciehp_pci.c69 * to avoid AB-BA deadlock with device_lock. in pciehp_configure_device()
121 * to avoid AB-BA deadlock with device_lock. in pciehp_unconfigure_device()
/linux/arch/microblaze/mm/
H A 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/drivers/net/ethernet/chelsio/cxgb/
H A Dtp.c14 /* Pause deadlock avoidance parameters */
42 * Enable pause frame deadlock prevention. in tp_init()
/linux/include/linux/
H A Dshrinker.h67 * is below shrinkable limit). No deadlock checks should be done during the
70 * deadlock condition is no longer pending.
/linux/tools/arch/powerpc/include/uapi/asm/
H A Derrno.h9 #define EDEADLOCK 58 /* File locking deadlock error */

12345678910>>...26