Bluetooth: Allow L2CAP getpeername() for BT_CONFIG state
authorJohan Hedberg <johan.hedberg@intel.com>
Tue, 1 Jul 2014 09:07:23 +0000 (12:07 +0300)
committerMarcel Holtmann <marcel@holtmann.org>
Thu, 3 Jul 2014 15:42:52 +0000 (17:42 +0200)
commitbf19d51b768ceeccab12f932cac73b60b1d20bab
tree560bc05fbc7f2b6e5eedf690f8f893750b9950af
parent26b0f4e2f9d022193039a72db09c048b9ae93459
Bluetooth: Allow L2CAP getpeername() for BT_CONFIG state

We have all the necessary remote information for getpeername() when we
are in the BT_CONFIG state so this should be allowed. This is
particularly important for LE sockets where changing the security level
will temporarily move the socket into BT_CONFIG state.

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