Bluetooth: Use real advertising state to random address update decision
Now that we have a flag for tracking the real advertising state we should use that to determine whether it's safe to update the random address or not. The couple of places that were clearing the flag due to a pending request need to be updated too. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
This commit is contained in:

committed by
Marcel Holtmann

parent
c93bd15033
commit
5ce194c4a7
@@ -1046,12 +1046,12 @@ static void enable_advertising(struct hci_request *req)
|
||||
u8 own_addr_type, enable = 0x01;
|
||||
bool connectable;
|
||||
|
||||
/* Clear the HCI_ADVERTISING bit temporarily so that the
|
||||
/* Clear the HCI_LE_ADV bit temporarily so that the
|
||||
* hci_update_random_address knows that it's safe to go ahead
|
||||
* and write a new random address. The flag will be set back on
|
||||
* as soon as the SET_ADV_ENABLE HCI command completes.
|
||||
*/
|
||||
clear_bit(HCI_ADVERTISING, &hdev->dev_flags);
|
||||
clear_bit(HCI_LE_ADV, &hdev->dev_flags);
|
||||
|
||||
connectable = get_connectable(hdev);
|
||||
|
||||
|
Reference in New Issue
Block a user