From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] b8773f: device: Fix privacy
Date: Wed, 01 Oct 2025 07:36:14 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1007714/000000-0166cf@github.com> (raw)
Branch: refs/heads/1007714
Home: https://github.com/bluez/bluez
Commit: b8773f54572fda61a982b430329db5457487aa3f
https://github.com/bluez/bluez/commit/b8773f54572fda61a982b430329db5457487aa3f
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-10-01 (Wed, 01 Oct 2025)
Changed paths:
M src/adapter.c
M src/device.c
M src/device.h
Log Message:
-----------
device: Fix privacy
In order for devices to properly be programmed into the adapter
resolving list they need to set the flag DEVICE_FLAG_ADDRESS_RESOLUTION
but that is only done if device_address_is_private return true but
currently it doesn't check the rpa flag which indicates that the address
has been updated to its identity.
While at it this also update the rpa flag to privacy to better indicate
the feature rather than just the address type and then introduces
device_set_privacy/device_get_privacy and replaces the usage of
device_address_is_private with device_get_privacy whenever the features
itself needs to be checked, rather than the current address type in use.
Fixes: https://github.com/bluez/bluez/issues/1079
Commit: 0166cf546ce875525f695d179c29427dac131e95
https://github.com/bluez/bluez/commit/0166cf546ce875525f695d179c29427dac131e95
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-10-01 (Wed, 01 Oct 2025)
Changed paths:
M src/adapter.c
M src/device.c
M src/device.h
Log Message:
-----------
core: Fix not resolving addresses
When using the likes of btd_adapter_get_device the address can sometimes
be the so called RPA which needs to be resolved in order to avoid
creating duplicated objects of the same device.
Note that normally the RPA are resolved in the kernel but there are
instances like BASS Add Source that may attempt to add a device direcly,
bypassing the GAP layer.
Compare: https://github.com/bluez/bluez/compare/b8773f54572f%5E...0166cf546ce8
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-10-01 14:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bluez/bluez/push/refs/heads/1007714/000000-0166cf@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox