- mutex-documentation-is-unclear-about-software-interrupts-tasklets-and-timers.patch removed from -mm tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The patch titled
     Mutex documentation is unclear about software interrupts, tasklets and timers
has been removed from the -mm tree.  Its filename was
     mutex-documentation-is-unclear-about-software-interrupts-tasklets-and-timers.patch

This patch was dropped because it was merged into mainline or a subsystem tree

------------------------------------------------------
Subject: Mutex documentation is unclear about software interrupts, tasklets and timers
From: Matti Linnanvuori <mattilinnanvuori@xxxxxxxxx>

Acked-by: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
Cc: Ingo Molnar <mingo@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---

 Documentation/mutex-design.txt |    3 ++-
 include/linux/mutex.h          |    3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff -puN Documentation/mutex-design.txt~mutex-documentation-is-unclear-about-software-interrupts-tasklets-and-timers Documentation/mutex-design.txt
--- a/Documentation/mutex-design.txt~mutex-documentation-is-unclear-about-software-interrupts-tasklets-and-timers
+++ a/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 -puN include/linux/mutex.h~mutex-documentation-is-unclear-about-software-interrupts-tasklets-and-timers include/linux/mutex.h
--- a/include/linux/mutex.h~mutex-documentation-is-unclear-about-software-interrupts-tasklets-and-timers
+++ a/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
_

Patches currently in -mm which might be from mattilinnanvuori@xxxxxxxxx are

origin.patch

-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Kernel Newbies FAQ]     [Kernel Archive]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Photo]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux