Bluetooth: Fix sending incorrect LE CoC PDU in BT_CONNECT2 state
authorJohan Hedberg <johan.hedberg@intel.com>
Thu, 13 Nov 2014 08:55:17 +0000 (10:55 +0200)
committerMarcel Holtmann <marcel@holtmann.org>
Sat, 15 Nov 2014 00:46:49 +0000 (01:46 +0100)
commitfa37c1aa30e538329b64dd55f401334f4bff47f5
tree308b45076f7c0f0600ab97c51d5e474759fc4a20
parenta809eff11f81e2dcf1e792586ef70693c60d7dc8
Bluetooth: Fix sending incorrect LE CoC PDU in BT_CONNECT2 state

For LE CoC L2CAP servers we don't do security level elevation during the
BT_CONNECT2 state (instead LE CoC simply sends an immediate error
response if the security level isn't high enough). Therefore if we get a
security level change while an LE CoC channel is in the BT_CONNECT2
state we should simply do nothing.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
net/bluetooth/l2cap_core.c