Hi Dean, On Sat, Jun 6, 2015 at 7:13 AM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: > Hi Dean, > >> Details of the issue are described in the thread >> [RFC] Bluetooth ERTM L2CAP deadlocks (hung tasks) due to l2cap_sock_shutdown() >> and kernel.org Bugzilla https://bugzilla.kernel.org/show_bug.cgi?id=99301 Are you still working on this? I can still lock bluetoothd on close, btw it seems you are not aware of the following: SO_LINGER When enabled, a close(2) or shutdown(2) will not return until all queued messages for the socket have been successfully sent or the linger timeout has been reached. Otherwise, the call returns immediately and the closing is done in the background. So according to the text above we should never call __l2cap_wait_ack on l2cap_sock_shutdown since it should return immediately, only when SO_LINGER is used it is allowed to block. Also there doesn't seems to be anything prevent us to send a L2CAP Disconnect request while there are unacked packets, at least I could find anything on the core about waiting for unacked nor the test spec has any test for it. -- Luiz Augusto von Dentz -- 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
