diff options
| author | Marcel Holtmann | 2013-10-13 17:50:41 +0200 |
|---|---|---|
| committer | Johan Hedberg | 2013-10-13 17:58:30 +0200 |
| commit | 4f1654e08464abad06487e173661cb73721d27a7 (patch) | |
| tree | 03906a24a3ad343060e5cec47f59513b3a4e6998 /crypto/testmgr.c | |
| parent | Bluetooth: Store address information in L2CAP channel structure (diff) | |
| download | kernel-qcow2-linux-4f1654e08464abad06487e173661cb73721d27a7.tar.gz kernel-qcow2-linux-4f1654e08464abad06487e173661cb73721d27a7.tar.xz kernel-qcow2-linux-4f1654e08464abad06487e173661cb73721d27a7.zip | |
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>
Diffstat (limited to 'crypto/testmgr.c')
0 files changed, 0 insertions, 0 deletions