[BLUETOOTH]: Fix locking in hci_sock_dev_event().
authorSatyam Sharma <ssatyam@cse.iitk.ac.in>
Thu, 17 May 2007 06:50:16 +0000 (23:50 -0700)
committerDavid S. Miller <davem@sunset.davemloft.net>
Thu, 17 May 2007 21:20:30 +0000 (14:20 -0700)
commit4ce61d1c7a8ef4c1337fa983a3036d4010e3c19e
treee7bf734478bc3f726d883439d5fdc44699d9a20a
parent689d79469b64662440a93ffbd1cbf994510bcbf6
[BLUETOOTH]: Fix locking in hci_sock_dev_event().

We presently use lock_sock() to acquire a lock on a socket in
hci_sock_dev_event(), but this goes BUG because lock_sock()
can sleep and we're already holding a read-write spinlock at
that point. So, we must use the non-sleeping BH version,
bh_lock_sock().

However, hci_sock_dev_event() is called from user context and
hence using simply bh_lock_sock() will deadlock against a
concurrent softirq that tries to acquire a lock on the same
socket. Hence, disabling BH's before acquiring the socket lock
and enable them afterwards, is the proper solution to fix
socket locking in hci_sock_dev_event().

Signed-off-by: Satyam Sharma <ssatyam@cse.iitk.ac.in>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/bluetooth/hci_sock.c