Public bug reported:

SRU Justification: This patch has been accepted into the upstream 2.6.27.4 
stable kernel.
It should be pulled into the Ubuntu kernel as well.

TEST CASE: TBD

commit 1b146f86965053c2496f9ce22c9e26a770930c66
Author: Mike Isely <[EMAIL PROTECTED]>
Date:   Sun Oct 19 16:26:05 2008 -0300

    V4L/DVB (9300): pvrusb2: Fix deadlock problem
    
    commit c82732a42896364296599b0f73f01c5e3fd781ae upstream
    
    Fix deadlock problem in 2.6.27 caused by new USB core behavior in
    response to a USB device reset request.  With older kernels, the USB
    device reset was "in line"; the reset simply took place and the driver
    retained its association with the hardware.  However now this reset
    triggers a disconnect, and worse still the disconnect callback happens
    in the context of the caller who asked for the device reset.  This
    results in an attempt by the pvrusb2 driver to recursively take a
    mutex it already has, which deadlocks the driver's worker thread.
    (Even if the disconnect callback were to happen on a different thread
    we'd still have problems however - because while the driver should
    survive and correctly disconnect / reconnect, it will then trigger
    another device reset during the repeated initialization, which will
    then cause another disconect, etc, forever.)  The fix here is simply
    to not attempt the device reset (it was of marginal value anyway).
    
    Signed-off-by: Mike Isely <[EMAIL PROTECTED]>
    Signed-off-by: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
    Signed-off-by: Mike Krufky <[EMAIL PROTECTED]>
    Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
V4L/DVB (9300): pvrusb2: Fix deadlock problem
https://bugs.launchpad.net/bugs/293995
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to