Bluetooth: Return the correct address type for L2CAP sockets
authorMarcel Holtmann <marcel@holtmann.org>
Sun, 13 Oct 2013 15:50:41 +0000 (08:50 -0700)
committerJohan Hedberg <johan.hedberg@intel.com>
Sun, 13 Oct 2013 15:58:30 +0000 (18:58 +0300)
commit4f1654e08464abad06487e173661cb73721d27a7
tree03906a24a3ad343060e5cec47f59513b3a4e6998
parent7eafc59e2f547fce3a31b3e2d03c14d57e9162b2
Bluetooth: Return the correct address type for L2CAP sockets

The L2CAP sockets can use BR/EDR public, LE public and LE random
addresses for various combinations of source and destination
devices. So make sure that getsockname(), getpeername() and
accept() return the correct address type.

For this the address type of the source and destination is stored
with the L2CAP channel information. The stored address type is
not the one specific for the HCI protocol. It is the address
type used for the L2CAP sockets and the management interface.

The underlying HCI connections store the HCI address type. If
needed, it gets converted to the socket address type.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
include/net/bluetooth/l2cap.h
net/bluetooth/l2cap_core.c
net/bluetooth/l2cap_sock.c
This page took 0.025051 seconds and 5 git commands to generate.