diff options
| author | Johan Hedberg <johan.hedberg@intel.com> | 2014-06-10 14:05:57 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-07-09 11:18:26 -0700 |
| commit | dc3048374bf4a8becb7d8b2c962c02166d28c6f0 (patch) | |
| tree | ce055194731a90d77c6b302293ebe013e3ccacbb /net/bluetooth | |
| parent | 43db39a6db7aa14302eea088abf1d1d88e60d608 (diff) | |
| download | linux-stable-dc3048374bf4a8becb7d8b2c962c02166d28c6f0.tar.gz linux-stable-dc3048374bf4a8becb7d8b2c962c02166d28c6f0.tar.bz2 linux-stable-dc3048374bf4a8becb7d8b2c962c02166d28c6f0.zip | |
Bluetooth: Fix indicating discovery state when canceling inquiry
commit 50143a433b70e3145bcf8a4a4e54f0c11bdee32b upstream.
When inquiry is canceled through the HCI_Cancel_Inquiry command there is
no Inquiry Complete event generated. Instead, all we get is the command
complete for the HCI_Inquiry_Cancel command. This means that we must
call the hci_discovery_set_state() function from the respective command
complete handler in order to ensure that user space knows the correct
discovery state.
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/bluetooth')
| -rw-r--r-- | net/bluetooth/hci_event.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c index fba31ab2c1c8..2e8c5765e5ea 100644 --- a/net/bluetooth/hci_event.c +++ b/net/bluetooth/hci_event.c @@ -48,6 +48,10 @@ static void hci_cc_inquiry_cancel(struct hci_dev *hdev, struct sk_buff *skb) smp_mb__after_clear_bit(); /* wake_up_bit advises about this barrier */ wake_up_bit(&hdev->flags, HCI_INQUIRY); + hci_dev_lock(hdev); + hci_discovery_set_state(hdev, DISCOVERY_STOPPED); + hci_dev_unlock(hdev); + hci_conn_check_pending(hdev); } |