diff options
| author | Jiri Slaby <jslaby@suse.cz> | 2013-01-03 19:53:53 +0400 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2013-01-06 16:42:33 +0400 |
| commit | a96fbe0429ace98bf3d92340ab9caa03c80db88c (patch) | |
| tree | 3af76c7fc2f066646b17dfcc183345d6dd04d91a /drivers/media/dvb-frontends/ts2020.c | |
| parent | 1c612e9a1cf712bd7845e3adb4961e3ef8eaf8aa (diff) | |
| download | linux-a96fbe0429ace98bf3d92340ab9caa03c80db88c.tar.xz | |
[media] dib0700: do not lock interruptible on tear-down paths
When mutex_lock_interruptible is used on paths where a signal can be
pending, the device is not closed properly and cannot be reused.
This usually happens when you start tzap for example and send it a
TERM signal. The signal is pending while tear-down routines are
called. Hence streaming is not properly stopped in that case. And
the device stops working from that moment on.
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'drivers/media/dvb-frontends/ts2020.c')
0 files changed, 0 insertions, 0 deletions