diff options
| author | Sonny Sasaka <sonnysasaka@chromium.org> | 2020-05-06 12:55:03 -0700 |
|---|---|---|
| committer | Marcel Holtmann <marcel@holtmann.org> | 2020-05-13 09:35:17 +0200 |
| commit | adf1d6926444029396861413aba8a0f2a805742a (patch) | |
| tree | 7800aa1cbf5e1c35c9b3db635cbdaba5bcff7409 /net/bluetooth/l2cap_sock.c | |
| parent | 608c39f4308cefde9d1f24b661261de2b3f3fef4 (diff) | |
| download | linux-adf1d6926444029396861413aba8a0f2a805742a.tar.gz linux-adf1d6926444029396861413aba8a0f2a805742a.tar.bz2 linux-adf1d6926444029396861413aba8a0f2a805742a.zip | |
Bluetooth: Handle Inquiry Cancel error after Inquiry Complete
After sending Inquiry Cancel command to the controller, it is possible
that Inquiry Complete event comes before Inquiry Cancel command complete
event. In this case the Inquiry Cancel command will have status of
Command Disallowed since there is no Inquiry session to be cancelled.
This case should not be treated as error, otherwise we can reach an
inconsistent state.
Example of a btmon trace when this happened:
< HCI Command: Inquiry Cancel (0x01|0x0002) plen 0
> HCI Event: Inquiry Complete (0x01) plen 1
Status: Success (0x00)
> HCI Event: Command Complete (0x0e) plen 4
Inquiry Cancel (0x01|0x0002) ncmd 1
Status: Command Disallowed (0x0c)
Signed-off-by: Sonny Sasaka <sonnysasaka@chromium.org>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'net/bluetooth/l2cap_sock.c')
0 files changed, 0 insertions, 0 deletions