Bluetooth: l2cap_disconnection_req priority over shutdown
authorDean Jenkins <Dean_Jenkins@mentor.com>
Wed, 14 Oct 2015 10:18:47 +0000 (12:18 +0200)
committerMarcel Holtmann <marcel@holtmann.org>
Tue, 20 Oct 2015 22:49:26 +0000 (00:49 +0200)
commit9f7378a9d6ced1784e08d3e21a9ddb769523baf2
tree500bf645b5dd1c47fc829697ec58a8e40f57a8c0
parent04ba72e6b24f1e0e2221fcd73f08782870473fa1
Bluetooth: l2cap_disconnection_req priority over shutdown

There is a L2CAP protocol race between the local peer and
the remote peer demanding disconnection of the L2CAP link.

When L2CAP ERTM is used, l2cap_sock_shutdown() can be called
from userland to disconnect L2CAP. However, there can be a
delay introduced by waiting for ACKs. During this waiting
period, the remote peer may have sent a Disconnection Request.
Therefore, recheck the shutdown status of the socket
after waiting for ACKs because there is no need to do
further processing if the connection has gone.

Signed-off-by: Dean Jenkins <Dean_Jenkins@mentor.com>
Signed-off-by: Harish Jenny K N <harish_kandiga@mentor.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
net/bluetooth/l2cap_sock.c