diff options
author | Mike Isely <isely@pobox.com> | 2008-10-19 16:26:05 -0300 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2008-10-21 14:20:51 -0200 |
commit | c82732a42896364296599b0f73f01c5e3fd781ae (patch) | |
tree | d2df3398f34b21420b27cc8a2885f7a2888cf53a /drivers/pcmcia/sa1100_assabet.c | |
parent | 9b4a7c8a83899ef7742f63c0e9a8a28cbff2c29a (diff) |
V4L/DVB (9300): pvrusb2: Fix deadlock problem
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 <isely@pobox.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'drivers/pcmcia/sa1100_assabet.c')
0 files changed, 0 insertions, 0 deletions