---

yaml --- r: 70670 b: refs/heads/master c: f20fda4 h: refs/heads/master v: v3
git-mirror · Oct 17, 2007 · df27990 · df27990
1 parent 2f685d2
commit df27990
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 3 deletions.
diff --git a/[refs] b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 1019f96d2d3aa4997d8055bd0c32c97f0fc21d06
+refs/heads/master: f20fda486164264e0c9a64f3256b3238d0dc78d7
diff --git a/trunk/Documentation/mutex-design.txt b/trunk/Documentation/mutex-design.txt
@@ -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:

diff --git a/trunk/include/linux/mutex.h b/trunk/include/linux/mutex.h
@@ -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