linux-kernel - Re: [PATCH 0/2] Add API to retrieve the Bluetooth Device Address (BD

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 20 Sep 2018 16:19:47 -0700
From:   Matthias Kaehlcke <mka@...omium.org>
To:     Sinan Kaya <okaya@...eaurora.org>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Rafael J . Wysocki" <rafael@...nel.org>,
        Sakari Ailus <sakari.ailus@...ux.intel.com>,
        Marcin Wojtas <mw@...ihalf.com>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Marcel Holtmann <marcel@...tmann.org>,
        Johan Hedberg <johan.hedberg@...il.com>,
        linux-kernel@...r.kernel.org, linux-bluetooth@...r.kernel.org,
        Balakrishna Godavarthi <bgodavar@...eaurora.org>,
        Loic Poulain <loic.poulain@...aro.org>,
        Brian Norris <briannorris@...omium.org>
Subject: Re: [PATCH 0/2] Add API to retrieve the Bluetooth Device Address
 (BD_ADDR)

On Thu, Sep 20, 2018 at 07:03:15PM -0400, Sinan Kaya wrote:
> On 9/20/2018 7:01 PM, Matthias Kaehlcke wrote:
> > Certainly true if this was the only driver. However another one will
> > follow soon and 'local-bd-address' is the official binding, so it's
> > not unlikely there will be more.
> 
> I was missing this information.

https://elixir.bootlin.com/linux/latest/source/Documentation/devicetree/bindings/net/bluetooth.txt

> Is there a way to convert existing users to this if any as well?

It depends.

If the existing users use a *really* reasonable name for the property
and use the same format it could be an option to add it to the lookup
besides 'local-bd-address', similar to what fwnode_get_mac_address()
does.

If the existing users populate a custom property with the BD address
in the bootloader you could roll out a bootloader change. You'd have
to make sure that bootloader and kernel match. The bootloader could
still populate the custom property to be compatible with 'old'
kernels.