| /linux-6.15/Documentation/admin-guide/aoe/ |
| H A D | todo.rst | 4 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-6.15/drivers/gpu/drm/nouveau/ |
| H A D | nouveau_backlight.c | 130 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-6.15/Documentation/locking/ |
| H A D | lockdep-design.rst | 131 lock will be attempted to acquire twice, which creates a deadlock,
132 referred to as lock recursion deadlock.
149 deadlock - as attempts to acquire the two locks form a circle which
289 lock related deadlock. [1]_
292 occur in practice to prove a deadlock: only the simple 'component'
402 to deadlock possibility.
440 it will get blocked by writer waiter B, and cause a self deadlock.
500 A deadlock case with recursive locks involved is as follow::
517 deadlock detection.
590 sufficient for deadlock detection.
[all …]
|
| H A D | ww-mutex-design.rst | 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-6.15/tools/memory-model/scripts/ |
| H A D | judgelitmus.sh | 131 echo " !!! Unexpected non-$outcome deadlock" $litmus
134 echo " !!! Unexpected non-$outcome deadlock" $litmus >> $LKMM_DESTDIR/$litmusout 2>&1
|
| /linux-6.15/scripts/coccinelle/api/ |
| H A D | stream_open.cocci | 6 // 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-6.15/Documentation/filesystems/ |
| H A D | directory-locking.rst | 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 D | fuse.rst | 184 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**::
385 **Scenario 2 - Tricky deadlock**
|
| H A D | locks.rst | 50 race and deadlock conditions that the current solution was the only
|
| H A D | journalling.rst | 73 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-6.15/drivers/gpu/drm/ci/xfails/ |
| H A D | amdgpu-stoney-skips.txt | 24 amdgpu/amd_deadlock@amdgpu-deadlock-sdma
|
| /linux-6.15/kernel/rcu/ |
| H A D | rcutorture.c | 3887 int cyclelen, int deadlock) in srcu_lockdep_next() argument
3892 j = deadlock ? 0 : -1; in srcu_lockdep_next()
3904 int deadlock; in rcu_torture_init_srcu_lockdep() local
3920 deadlock = test_srcu_lockdep / 1000; in rcu_torture_init_srcu_lockdep()
3924 if (WARN_ONCE(deadlock != !!deadlock, in rcu_torture_init_srcu_lockdep()
3926 __func__, test_srcu_lockdep, deadlock)) in rcu_torture_init_srcu_lockdep()
3938 if (deadlock && cyclelen == 1) in rcu_torture_init_srcu_lockdep()
3942 "srcu_read_unlock", i, cyclelen, deadlock); in rcu_torture_init_srcu_lockdep()
3963 "mutex_unlock", i, cyclelen, deadlock); in rcu_torture_init_srcu_lockdep()
3984 "up_write", i, cyclelen, deadlock); in rcu_torture_init_srcu_lockdep()
[all …]
|
| /linux-6.15/Documentation/arch/arm/ |
| H A D | swp_emulation.rst | 26 cause programs that perform SWP operations to uncached memory to deadlock, as
|
| /linux-6.15/Documentation/RCU/ |
| H A D | UP.rst | 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 D | whatisRCU.rst | 656 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!
1214 Why is this argument naive? How could a deadlock
1237 One way to avoid this deadlock is to use an approach like
1242 release rcu_gp_mutex, avoiding the deadlock.
1244 Even in the absence of deadlock, this RCU implementation
|
| /linux-6.15/Documentation/ABI/removed/ |
| H A D | sysfs-mce | 22 risk of deadlock. Higher tolerant values trade potentially
|
| /linux-6.15/Documentation/devicetree/bindings/fpga/ |
| H A D | xlnx,pr-decoupler.yaml | 26 preventing the system deadlock that can occur if AXI transactions are
|
| /linux-6.15/drivers/gpu/drm/nouveau/dispnv50/ |
| H A D | crc.c | 587 goto deadlock; in nv50_crc_set_source()
597 goto deadlock; in nv50_crc_set_source()
621 deadlock: in nv50_crc_set_source()
|
| /linux-6.15/tools/memory-model/ |
| H A D | lock.cat | 53 * inside a critical section (for the same lock) always deadlock.
81 (* Allow up to one unmatched LKW per location; more must deadlock *)
|
| /linux-6.15/arch/arm/ |
| H A D | Kconfig | 576 bool "ARM errata: Processor deadlock when a false hazard is created"
584 hazard might then cause a processor deadlock. The workaround enables
760 to deadlock. This workaround puts DSB before executing ISB if
788 instruction might deadlock. Fixed in r0p1.
790 lead to either a data corruption or a CPU deadlock. Not fixed in
804 deadlock when the VMOV instructions are issued out-of-order.
807 bool "ARM errata: A12: DMB NSHST/ISHST mixed ... might cause deadlock"
813 and Device/Strongly-Ordered loads and stores might cause deadlock
816 bool "ARM errata: A12: CPU might deadlock under some very rare internal conditions"
838 lead to either a data corruption or a CPU deadlock. Not fixed in
[all …]
|
| /linux-6.15/Documentation/networking/ |
| H A D | driver.rst | 122 This error can deadlock sockets waiting for send buffer room
|
| /linux-6.15/Documentation/core-api/ |
| H A D | gfp_mask-from-fs-io.rst | 19 The traditional way to avoid this deadlock problem is to clear __GFP_FS
|
| /linux-6.15/Documentation/i2c/ |
| H A D | i2c-topology.rst | 132 __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-6.15/Documentation/infiniband/ |
| H A D | core_locking.rst | 108 semaphores that could cause deadlock if a consumer calls back into
|
| /linux-6.15/Documentation/admin-guide/device-mapper/ |
| H A D | dm-raid.rst | 411 1.12.1 Fix for MD deadlock between mddev_suspend() and md_write_start() available
413 1.13.1 Fix deadlock caused by early md_stop_writes(). Also fix size an
417 deadlock/potential data corruption. Update superblock when
|