rpms/kernel/F-8 linux-2.6-usb-serial-fix-recursive-lock.patch, 1.1, 1.2

[Chuck Ebbert (cebbert)]

Author: cebbert

Update of /cvs/pkgs/rpms/kernel/F-8
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10536

Modified Files:
	linux-2.6-usb-serial-fix-recursive-lock.patch 
Log Message:
use official commit


linux-2.6-usb-serial-fix-recursive-lock.patch:

Index: linux-2.6-usb-serial-fix-recursive-lock.patch
===================================================================
RCS file: /cvs/pkgs/rpms/kernel/F-8/linux-2.6-usb-serial-fix-recursive-lock.patch,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- linux-2.6-usb-serial-fix-recursive-lock.patch	10 Mar 2008 22:27:36 -0000	1.1
+++ linux-2.6-usb-serial-fix-recursive-lock.patch	12 Mar 2008 18:34:38 -0000	1.2
@@ -1,31 +1,33 @@
-From zaitcev at redhat.com  Wed Mar  5 11:39:23 2008
-From: Pete Zaitcev <zaitcev at redhat.com>
-Date: Tue, 4 Mar 2008 23:28:42 -0800
-Subject: USB: fix usb-serial generic recursive lock
-To: greg at kroah.com
-Cc: zaitcev at redhat.com, linux-usb at vger.kernel.org
-Message-ID: <20080304232842.c783d383.zaitcev at redhat.com>
-
-
-Nobody should be using the generic usb-serial for anything other than
-testing. Still, it's not a good thing that it's easy to lock up. There
-is a traceback from NMI oopser here:
- https://bugzilla.redhat.com/show_bug.cgi?id=431379
-
-But in short, if a line discipline has a chance to echo anything, input
-can loop back a write method. So, don't call tty_flip_buffer_push from
-under a lock taken on write path.
-
-Signed-off-by: Pete Zaitcev <zaitcev at redhat.com>
-Signed-off-by: Greg Kroah-Hartman <gregkh at suse.de>
-
+Gitweb:     http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b507cc9710d8b6e3013468b40522e235342fc84a
+Commit:     b507cc9710d8b6e3013468b40522e235342fc84a
+Parent:     cdeeeae056a429e729ae9e914fa8142ee45bee93
+Author:     Pete Zaitcev <zaitcev at redhat.com>
+AuthorDate: Tue Mar 4 23:28:42 2008 -0800
+Committer:  Greg Kroah-Hartman <gregkh at suse.de>
+CommitDate: Mon Mar 10 16:42:25 2008 -0700
+
+    USB: fix usb-serial generic recursive lock
+    
+    Nobody should be using the generic usb-serial for anything other than
+    testing. Still, it's not a good thing that it's easy to lock up. There
+    is a traceback from NMI oopser here:
+     https://bugzilla.redhat.com/show_bug.cgi?id=431379
+    
+    But in short, if a line discipline has a chance to echo anything, input
+    can loop back a write method. So, don't call tty_flip_buffer_push from
+    under a lock taken on write path.
+    
+    Signed-off-by: Pete Zaitcev <zaitcev at redhat.com>
+    Signed-off-by: Greg Kroah-Hartman <gregkh at suse.de>
 ---
  drivers/usb/serial/generic.c |   10 ++++++----
- 1 file changed, 6 insertions(+), 4 deletions(-)
+ 1 files changed, 6 insertions(+), 4 deletions(-)
 
+diff --git a/drivers/usb/serial/generic.c b/drivers/usb/serial/generic.c
+index 97fa3c4..7cfce9d 100644
 --- a/drivers/usb/serial/generic.c
 +++ b/drivers/usb/serial/generic.c
-@@ -323,7 +323,7 @@ static void flush_and_resubmit_read_urb 
+@@ -323,7 +323,7 @@ static void flush_and_resubmit_read_urb (struct usb_serial_port *port)
  		room = tty_buffer_request_room(tty, urb->actual_length);
  		if (room) {
  			tty_insert_flip_string(tty, urb->transfer_buffer, room);
@@ -34,7 +36,7 @@
  		}
  	}
  
-@@ -349,10 +349,12 @@ void usb_serial_generic_read_bulk_callba
+@@ -349,10 +349,12 @@ void usb_serial_generic_read_bulk_callback (struct urb *urb)
  
  	/* Throttle the device if requested by tty */
  	spin_lock_irqsave(&port->lock, flags);