The patch titled
     Char: mxser_new, fix recursive locking
has been removed from the -mm tree.  Its filename was
     char-mxser_new-fix-recursive-locking.patch

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

------------------------------------------------------
Subject: Char: mxser_new, fix recursive locking
From: Jan Yenya Kasprzak <[EMAIL PROTECTED]>

Signed-off-by: Jan "Yenya" Kasprzak <[EMAIL PROTECTED]>
Acked-by: Jiri Slaby <[EMAIL PROTECTED]>
Acked-by: Alan Cox <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 drivers/char/mxser_new.c |    7 +++++++
 1 file changed, 7 insertions(+)

diff -puN drivers/char/mxser_new.c~char-mxser_new-fix-recursive-locking 
drivers/char/mxser_new.c
--- a/drivers/char/mxser_new.c~char-mxser_new-fix-recursive-locking
+++ a/drivers/char/mxser_new.c
@@ -2230,7 +2230,14 @@ end_intr:
        port->mon_data.rxcnt += cnt;
        port->mon_data.up_rxcnt += cnt;
 
+       /*
+        * We are called from an interrupt context with &port->slock
+        * being held. Drop it temporarily in order to prevent
+        * recursive locking.
+        */
+       spin_unlock(&port->slock);
        tty_flip_buffer_push(tty);
+       spin_lock(&port->slock);
 }
 
 static void mxser_transmit_chars(struct mxser_port *port)
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

origin.patch

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

Reply via email to