Messages in this thread Patch in this message | | | Date | Thu, 1 Apr 2021 11:11:33 +0800 | Subject | [PATCH] Bluetooth: Check inquiry status before sending one | From | Archie Pusaka <> |
| |
From: Archie Pusaka <apusaka@chromium.org>
There is a possibility where HCI_INQUIRY flag is set but we still send HCI_OP_INQUIRY anyway.
Such a case can be reproduced by connecting to an LE device while active scanning. When the device is discovered, we initiate a connection, stop LE Scan, and send Discovery MGMT with status disabled, but we don't cancel the inquiry.
Signed-off-by: Archie Pusaka <apusaka@chromium.org> Reviewed-by: Sonny Sasaka <sonnysasaka@chromium.org> ---
net/bluetooth/hci_request.c | 3 +++ 1 file changed, 3 insertions(+)
diff --git a/net/bluetooth/hci_request.c b/net/bluetooth/hci_request.c index 8ace5d34b01e..5a5ec7ed15ea 100644 --- a/net/bluetooth/hci_request.c +++ b/net/bluetooth/hci_request.c @@ -2952,6 +2952,9 @@ static int bredr_inquiry(struct hci_request *req, unsigned long opt) const u8 liac[3] = { 0x00, 0x8b, 0x9e }; struct hci_cp_inquiry cp; + if (test_bit(HCI_INQUIRY, &req->hdev->flags)) + return 0; + bt_dev_dbg(req->hdev, ""); hci_dev_lock(req->hdev); -- 2.31.0.291.g576ba9dcdaf-goog
| |