Re: [PATCH v5] Bluetooth: MGMT: Fix discovery stuck after a failed Stop Discovery

[patchwork-bot+bluetooth]

Hello:

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

On Mon,  2 Nov 2026 09:00:00 -0800 you wrote:
> Stop Discovery moves the discovery to DISCOVERY_STOPPING, and
> stop_discovery_complete() only moves it on to DISCOVERY_STOPPED when
> stopping succeeded. When it fails, for example because LE Set Scan
> Enable times out, nothing moves the discovery out of
> DISCOVERY_STOPPING: Stop Discovery is rejected, as the discovery is not
> active anymore, and the LE scan timeout was cancelled before the scan
> was disabled. Until the controller is powered off, every Start
> Discovery then fails with Busy, and hci_update_passive_scan_sync()
> skips background scanning, so devices set to auto-connect are not
> connected anymore.
> 
> [...]

Here is the summary with links:
  - [v5] Bluetooth: MGMT: Fix discovery stuck after a failed Stop Discovery
    https://git.kernel.org/bluetooth/bluetooth-next/c/60b10121db60

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