Hi Marcel, On Sun, Oct 13, 2013, Marcel Holtmann wrote: > 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@xxxxxxxxxxxx> > --- > include/net/bluetooth/l2cap.h | 5 +++-- > net/bluetooth/l2cap_core.c | 18 ++++++++++++++++++ > net/bluetooth/l2cap_sock.c | 3 +++ > 3 files changed, 24 insertions(+), 2 deletions(-) Applied to bluetooth-next. Thanks. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
