Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit f20fda48 authored by Matti Linnanvuori's avatar Matti Linnanvuori Committed by Linus Torvalds
Browse files

Mutex documentation is unclear about software interrupts, tasklets and timers 



Acked-by: default avatarArjan van de Ven <arjan@linux.intel.com>
Cc: Ingo Molnar <mingo@elte.hu>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent 1019f96d

Documentation/mutex-design.txt

+2 −1
Original line number Diff line number Diff line
@@ -90,7 +90,8 @@ of advantages of mutexes: 
   * - task may not exit with mutex held

   * - memory areas where held locks reside must not be freed

   * - held mutexes must not be reinitialized

   * - mutexes may not be used in irq contexts

   * - mutexes may not be used in hardware or software interrupt

   *   contexts such as tasklets and timers



   furthermore, there are also convenience features in the debugging

   code:

include/linux/mutex.h

+2 −1
Original line number Diff line number Diff line
@@ -29,7 +29,8 @@ 
 * - task may not exit with mutex held

 * - memory areas where held locks reside must not be freed

 * - held mutexes must not be reinitialized

 * - mutexes may not be used in irq contexts

 * - mutexes may not be used in hardware or software interrupt

 *   contexts such as tasklets and timers

 *

 * These semantics are fully enforced when DEBUG_MUTEXES is

 * enabled. Furthermore, besides enforcing the above rules, the mutex