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>

1 files changed, 2 insertions, 1 deletions

diff --git a/net/bluetooth/l2cap_sock.c b/net/bluetooth/l2cap_sock.c
index bf72886de6ef..9bb4d1b3a483 100644
--- a/net/bluetooth/l2cap_sock.c
+++ b/net/bluetooth/l2cap_sock.c
@@ -361,7 +361,8 @@ static int l2cap_sock_getname(struct socket *sock, struct sockaddr *addr,
         BT_DBG("sock %p, sk %p", sock, sk);
 
         if (peer && sk->sk_state != BT_CONNECTED &&
-            sk->sk_state != BT_CONNECT && sk->sk_state != BT_CONNECT2)
+            sk->sk_state != BT_CONNECT && sk->sk_state != BT_CONNECT2 &&
+            sk->sk_state != BT_CONFIG)
                 return -ENOTCONN;
 
         memset(la, 0, sizeof(struct sockaddr_l2));