Home
last modified time | relevance | path

Searched refs:deadlock (Results 1 – 25 of 49) sorted by relevance

12

/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/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/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.rst20 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/tools/memory-model/scripts/
H A Djudgelitmus.sh131 echo " !!! Unexpected non-$outcome deadlock" $litmus
134 echo " !!! Unexpected non-$outcome deadlock" $litmus >> $LKMM_DESTDIR/$litmusout 2>&1
/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/Documentation/filesystems/
H A Ddirectory-locking.rst133 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 Dlocks.rst50 race and deadlock conditions that the current solution was the only
H A Djournalling.rst73 deadlock. The first thing to note is that each task can only have a
91 behaviour to jbd2_journal_start() so you can deadlock here just as
/linux/kernel/rcu/
H A Drcutorture.c4293 int cyclelen, int deadlock) in srcu_lockdep_next() argument
4298 j = deadlock ? 0 : -1; in srcu_lockdep_next()
4310 int deadlock; in rcu_torture_init_srcu_lockdep() local
4326 deadlock = test_srcu_lockdep / 1000; in rcu_torture_init_srcu_lockdep()
4330 if (WARN_ONCE(deadlock != !!deadlock, in rcu_torture_init_srcu_lockdep()
4332 __func__, test_srcu_lockdep, deadlock)) in rcu_torture_init_srcu_lockdep()
4343 __func__, test_srcu_lockdep, cyclelen, deadlock ? "" : "non-"); in rcu_torture_init_srcu_lockdep()
4344 if (deadlock && cyclelen == 1) in rcu_torture_init_srcu_lockdep()
4348 "srcu_read_unlock", i, cyclelen, deadlock); in rcu_torture_init_srcu_lockdep()
4359 __func__, test_srcu_lockdep, cyclelen, deadlock ? "" : "non-"); in rcu_torture_init_srcu_lockdep()
[all …]
/linux/Documentation/RCU/
H A DUP.rst62 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.rst659 you allow nested rcu_read_lock() calls, you can deadlock.
715 from deadlock (an important property of RCU). The reason for this is
718 so there can be no deadlock cycle.
723 Why is this argument naive? How could a deadlock
725 kernel? How could this deadlock be avoided?
754 participate in a deadlock cycle!
1306 Why is this argument naive? How could a deadlock
1329 One way to avoid this deadlock is to use an approach like
1334 release rcu_gp_mutex, avoiding the deadlock.
1336 Even in the absence of deadlock, this RCU implementation
H A Drcu.rst27 acquire locks can also greatly simplify deadlock-avoidance code.
/linux/Documentation/arch/arm/
H A Dswp_emulation.rst26 cause programs that perform SWP operations to uncached memory to deadlock, as
/linux/Documentation/ABI/removed/
H A Dsysfs-mce22 risk of deadlock. Higher tolerant values trade potentially
/linux/Documentation/filesystems/fuse/
H A Dfuse.rst198 c) Accidental deadlock
200 d) Malicious deadlock
378 There are a couple of ways in which to deadlock a FUSE filesystem.
382 **Scenario 1 - Simple deadlock**::
399 **Scenario 2 - Tricky deadlock**
/linux/tools/memory-model/
H A Dlock.cat53 * inside a critical section (for the same lock) always deadlock.
81 (* Allow up to one unmatched LKW per location; more must deadlock *)
H A DREADME214 and following releases and checking for self-deadlock.
/linux/arch/arm/
H A DKconfig573 bool "ARM errata: Processor deadlock when a false hazard is created"
581 hazard might then cause a processor deadlock. The workaround enables
751 bool "ARM errata: A data cache maintenance operation which aborts, might lead to deadlock"
757 to deadlock. This workaround puts DSB before executing ISB if
780 bool "ARM errata: A12: some seqs of opposed cond code instrs => deadlock or corruption"
785 instruction might deadlock. Fixed in r0p1.
787 lead to either a data corruption or a CPU deadlock. Not fixed in
801 deadlock when the VMOV instructions are issued out-of-order.
804 bool "ARM errata: A12: DMB NSHST/ISHST mixed ... might cause deadlock"
810 and Device/Strongly-Ordered loads and stores might cause deadlock
[all …]
/linux/Documentation/networking/
H A Ddriver.rst122 This error can deadlock sockets waiting for send buffer room
/linux/Documentation/i2c/
H A Di2c-topology.rst132 __i2c_transfer), or a deadlock will follow.
156 that they do not deadlock the root adapter.
158 unlocked I2C transfer, so that it does not deadlock the parent
/linux/Documentation/infiniband/
H A Dcore_locking.rst108 semaphores that could cause deadlock if a consumer calls back into
/linux/arch/arm/mach-omap2/
H A DKconfig268 system to deadlock.
/linux/Documentation/devicetree/bindings/iommu/
H A Diommu.txt111 domain, leading to a deadlock.
/linux/fs/jffs2/
H A DREADME.Locking55 lead to deadlock, unless we played games with unlocking the i_sem

12