Bluetooth: Fix returning peer address in pending connect state
authorJohan Hedberg <johan.hedberg@intel.com>
Wed, 26 Mar 2014 13:49:18 +0000 (15:49 +0200)
committerMarcel Holtmann <marcel@holtmann.org>
Wed, 26 Mar 2014 16:31:33 +0000 (09:31 -0700)
commite8b1ab9e6d30394e0df3e4f60bf56c4dc9bf0863
treed3695da156cb780b4fee75d76168e85abd5a46dc
parent8396215d4865d66be9cdfcec8d135862e1fd98d1
Bluetooth: Fix returning peer address in pending connect state

We should let user space request the peer address also in the pending
connect states, i.e. BT_CONNECT and BT_CONNECT2. There is existing user
space code that tries to do this and will fail without extending the set
of allowed states for the peer address information.

This patch adds the two states to the allowed ones in the L2CAP and
RFCOMM sock_getname functions, thereby preventing ENOTCONN from being
returned.

Reported-by: Andrzej Kaczmarek <andrzej.kaczmarek@tieto.com>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Tested-by: Andrzej Kaczmarek <andrzej.kaczmarek@tieto.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
net/bluetooth/l2cap_sock.c
net/bluetooth/rfcomm/sock.c