| /Linux-v6.6/Documentation/admin-guide/aoe/ |
| 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-v6.6/drivers/gpu/drm/nouveau/ |
| D | nouveau_backlight.c | 166 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/Documentation/locking/ |
| D | lockdep-design.rst | 129 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 …]
|
| 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-v6.6/tools/memory-model/scripts/ |
| D | judgelitmus.sh | 131 echo " !!! Unexpected non-$outcome deadlock" $litmus
134 echo " !!! Unexpected non-$outcome deadlock" $litmus >> $LKMM_DESTDIR/$litmusout 2>&1
|
| /Linux-v6.6/scripts/coccinelle/api/ |
| D | stream_open.cocci | 6 // 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/Documentation/filesystems/ |
| D | directory-locking.rst | 66 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.
|
| 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**
|
| D | locks.rst | 50 race and deadlock conditions that the current solution was the only
|
| 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-v6.6/kernel/rcu/ |
| D | rcutorture.c | 3526 int cyclelen, int deadlock) in srcu_lockdep_next() argument
3531 j = deadlock ? 0 : -1; in srcu_lockdep_next()
3543 int deadlock; in rcu_torture_init_srcu_lockdep() local
3559 deadlock = test_srcu_lockdep / 1000; in rcu_torture_init_srcu_lockdep()
3563 if (WARN_ONCE(deadlock != !!deadlock, in rcu_torture_init_srcu_lockdep()
3565 __func__, test_srcu_lockdep, deadlock)) in rcu_torture_init_srcu_lockdep()
3576 __func__, test_srcu_lockdep, cyclelen, deadlock ? "" : "non-"); in rcu_torture_init_srcu_lockdep()
3577 if (deadlock && cyclelen == 1) in rcu_torture_init_srcu_lockdep()
3581 "srcu_read_unlock", i, cyclelen, deadlock); in rcu_torture_init_srcu_lockdep()
3592 __func__, test_srcu_lockdep, cyclelen, deadlock ? "" : "non-"); in rcu_torture_init_srcu_lockdep()
[all …]
|
| /Linux-v6.6/Documentation/arch/arm/ |
| D | swp_emulation.rst | 26 cause programs that perform SWP operations to uncached memory to deadlock, as
|
| /Linux-v6.6/Documentation/RCU/ |
| 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.
|
| D | whatisRCU.rst | 637 you allow nested rcu_read_lock() calls, you can deadlock.
693 from deadlock (an important property of RCU). The reason for this is
696 so there can be no deadlock cycle.
701 Why is this argument naive? How could a deadlock
703 kernel? How could this deadlock be avoided?
732 participate in a deadlock cycle!
1185 Why is this argument naive? How could a deadlock
1208 One way to avoid this deadlock is to use an approach like
1213 release rcu_gp_mutex, avoiding the deadlock.
1215 Even in the absence of deadlock, this RCU implementation
|
| D | rcu.rst | 27 acquire locks can also greatly simplify deadlock-avoidance code.
|
| /Linux-v6.6/Documentation/ABI/removed/ |
| D | sysfs-mce | 22 risk of deadlock. Higher tolerant values trade potentially
|
| /Linux-v6.6/drivers/gpu/drm/nouveau/dispnv50/ |
| D | crc.c | 585 goto deadlock; in nv50_crc_set_source()
595 goto deadlock; in nv50_crc_set_source()
619 deadlock: in nv50_crc_set_source()
|
| /Linux-v6.6/tools/memory-model/ |
| D | lock.cat | 53 * inside a critical section (for the same lock) always deadlock.
75 (* Allow up to one unmatched LKW per location; more must deadlock *)
|
| /Linux-v6.6/arch/arm/ |
| D | Kconfig | 651 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/Documentation/networking/ |
| D | driver.rst | 122 This error can deadlock sockets waiting for send buffer room
|
| /Linux-v6.6/Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 19 The traditional way to avoid this deadlock problem is to clear __GFP_FS
|
| /Linux-v6.6/Documentation/i2c/ |
| 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-v6.6/Documentation/infiniband/ |
| D | core_locking.rst | 108 semaphores that could cause deadlock if a consumer calls back into
|
| /Linux-v6.6/Documentation/admin-guide/device-mapper/ |
| 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
|
| /Linux-v6.6/arch/arm/mach-omap2/ |
| D | Kconfig | 268 system to deadlock.
|
