diff options
| author | Mat Martineau <mathewm@codeaurora.org> | 2011-12-07 04:23:26 +0400 |
|---|---|---|
| committer | Gustavo F. Padovan <padovan@profusion.mobi> | 2011-12-19 04:29:35 +0400 |
| commit | 79e654787c67f6b05f73366ff8ccac72ba7249e6 (patch) | |
| tree | c1a498c2af15b6df2387898ac260c84f4a4dbbd1 /lib/spinlock_debug.c | |
| parent | 36e999a83a4a4badd389901eb6d23a30e199b8db (diff) | |
| download | linux-79e654787c67f6b05f73366ff8ccac72ba7249e6.tar.xz | |
Bluetooth: Clear RFCOMM session timer when disconnecting last channel
When the last RFCOMM data channel is closed, a timer is normally set
up to disconnect the control channel at a later time. If the control
channel disconnect command is sent with the timer pending, the timer
needs to be cancelled.
If the timer is not cancelled in this situation, the reference
counting logic for the RFCOMM session does not work correctly when the
remote device closes the L2CAP connection. The session is freed at
the wrong time, leading to a kernel panic.
Signed-off-by: Mat Martineau <mathewm@codeaurora.org>
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
Diffstat (limited to 'lib/spinlock_debug.c')
0 files changed, 0 insertions, 0 deletions