Eric Lee / smarc-ti-linux-kernel

Download as
Browse Code ยป

Commit f20fda486164264e0c9a64f3256b3238d0dc78d7

Authored by Matti Linnanvuori
Committed by Linus Torvalds
1 parent 1019f96d2d

Mutex documentation is unclear about software interrupts, tasklets and timers 

Acked-by: Arjan van de Ven <arjan@linux.intel.com>
Cc: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

Showing 2 changed files with 4 additions and 2 deletions Side-by-side Diff

Documentation/mutex-design.txt
Diff comments   View file @ f20fda4
... ... @@ -90,7 +90,8 @@
90 90 * - task may not exit with mutex held
91 91 * - memory areas where held locks reside must not be freed
92 92 * - held mutexes must not be reinitialized
93   - * - mutexes may not be used in irq contexts
  93 + * - mutexes may not be used in hardware or software interrupt
  94 + * contexts such as tasklets and timers
94 95  
95 96 furthermore, there are also convenience features in the debugging
96 97 code:
include/linux/mutex.h
Diff comments   View file @ f20fda4
... ... @@ -29,7 +29,8 @@
29 29 * - task may not exit with mutex held
30 30 * - memory areas where held locks reside must not be freed
31 31 * - held mutexes must not be reinitialized
32   - * - mutexes may not be used in irq contexts
  32 + * - mutexes may not be used in hardware or software interrupt
  33 + * contexts such as tasklets and timers
33 34 *
34 35 * These semantics are fully enforced when DEBUG_MUTEXES is
35 36 * enabled. Furthermore, besides enforcing the above rules, the mutex