Re: [PATCH v3 0/2] Bluetooth: dial the address the peer is actually on air with

[patchwork-bot+bluetooth]

Hello:

This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx>:

On Wed, 09 Sep 2026 00:29:35 +0200 you wrote:
> An identity address only reaches a peer advertising an RPA if the
> controller resolves it for us; where it cannot, the host has to dial the
> peer's on-air address itself. v2 did that by keeping the RPA in conn->dst
> when the controller will not translate, which Luiz asked for and which
> holds for as long as the peer is still using that RPA.
> 
> It does not hold once a peer turns privacy off. hci_connect_le() swaps in
> the cached RPA whenever the IRK has one, nothing ever clears that cache,
> and a peer that stops sending RPAs stops producing the reports that would
> refresh it. Before this series the conversion in __hci_conn_add() hid the
> problem by turning the stale RPA back into the identity address; keeping
> the RPA exposes it, and every connect attempt goes to an address the peer
> has abandoned.
> 
> [...]

Here is the summary with links:
  - [v3,1/2] Bluetooth: forget a peer's RPA once it advertises its identity address
    https://git.kernel.org/bluetooth/bluetooth-next/c/fb3a817741b1
  - [v3,2/2] Bluetooth: put the peer's on-air address on air when we cannot resolve
    https://git.kernel.org/bluetooth/bluetooth-next/c/e35544d23359

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html