Bluetooth: Fix EBUSY condition test in l2cap_chan_connect
authorJohan Hedberg <johan.hedberg@intel.com>
Mon, 29 Apr 2013 16:35:37 +0000 (19:35 +0300)
committerGustavo Padovan <gustavo.padovan@collabora.co.uk>
Sat, 22 Jun 2013 23:23:47 +0000 (00:23 +0100)
commit141d57065afd11977c4d346f64b25350445bf689
treec33d9f462442a3916c7bdb270975836c5be71d33
parentf224ca5fc207a9957164e6f42ec6766da0f55d54
Bluetooth: Fix EBUSY condition test in l2cap_chan_connect

The current test in l2cap_chan_connect is intended to protect against
multiple conflicting connect attempts. However, it assumes that there
will ever only be a single CID that is connected to, which is not true.
We do need to check for conflicts with connect attempts to the same
destination CID but this check is not in anyway specific to LE but can
be applied to BR/EDR as well.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
net/bluetooth/l2cap_core.c