xavi/android_kernel_m2note/net/bluetooth/l2cap_sock.c, branch ng-7.1.2

Bluetooth: Release locks before sleeping for L2CAP socket shutdown

2017-04-11T08:59:09+00:00

If there are unacknowledged frames during an ongoing L2CAP transfer and if socket is shutdown, it will result in deadlock as locks are not released before going to sleep. The L2CAP receive thread will be waiting on locks to update unacknowledged frame count, whereas socket shutdown thread will be sleeping till unacknowledged count becomes 0 resulting in deadlock. Signed-off-by: Rupesh Tatiya

Bluetooth: Return the correct address type for L2CAP sockets

2017-04-11T08:59:08+00:00

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 Signed-off-by: Johan Hedberg Signed-off-by: Kamal Negi

Bluetooth: remove unnecessary check on BT_CLOSED socks during accept

2017-04-11T08:59:07+00:00

BT_CLOSED sockets are unlinked from teardown callback. Trying to unlink such sockets from bt_accept_dequeue may lead to NULL dereference as teardown callback does not hold lock for parent sock. bt_accept_unlink may be called from two threads, resulting in incorrect socket ref count. Return if parent is NULL. Signed-off-by: Rupesh Tatiya

3.10.102-> 3.10.103

2016-09-09T22:45:11+00:00

first commit

2016-08-15T02:19:42+00:00