Bluetooth: Support static address when BR/EDR has been disabled

Every BR/EDR/LE dual-mode controller requires to have a public address
and so far that has become the identity address and own address. The
only way to change that behavior was with a force_static_address
debugfs option.

However the host can actually disable the BR/EDR part of a dual-mode
controller and turn into a single mode LE controller. In that case
it makes perfect sense for a host to use a chosen static address
instead of the public address.

So if the host disables BR/EDR and configures a static address, then
that static address is used as identity address and own address. If
the host does not configure a static address, then the public address
is used as before.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>

1 files changed, 7 insertions, 1 deletions

diff --git a/net/bluetooth/hci_request.c b/net/bluetooth/hci_request.c
index 5e64ea70a106..324c6418b17c 100644
--- a/net/bluetooth/hci_request.c
+++ b/net/bluetooth/hci_request.c
@@ -378,9 +378,15 @@ int hci_update_random_address(struct hci_request *req, bool require_privacy,
          * address use the static address as random address (but skip
          * the HCI command if the current random address is already the
          * static one.
+         *
+         * In case BR/EDR has been disabled on a dual-mode controller
+         * and a static address has been configured, then use that
+         * address instead of the public BR/EDR address.
          */
         if (test_bit(HCI_FORCE_STATIC_ADDR, &hdev->dbg_flags) ||
-            !bacmp(&hdev->bdaddr, BDADDR_ANY)) {
+            !bacmp(&hdev->bdaddr, BDADDR_ANY) ||
+            (!test_bit(HCI_BREDR_ENABLED, &hdev->dev_flags) &&
+             bacmp(&hdev->static_addr, BDADDR_ANY))) {
                 *own_addr_type = ADDR_LE_DEV_RANDOM;
                 if (bacmp(&hdev->static_addr, &hdev->random_addr))
                         hci_req_add(req, HCI_OP_LE_SET_RANDOM_ADDR, 6,