Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx>:
On Tue, 10 Jan 2023 17:22:53 -0800 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx>
>
> This fixes the following trace caused by attempting to lock
> cmd_sync_work_lock while holding the rcu_read_lock:
>
> kworker/u3:2/212 is trying to lock:
> ffff888002600910 (&hdev->cmd_sync_work_lock){+.+.}-{3:3}, at:
> hci_cmd_sync_queue+0xad/0x140
> other info that might help us debug this:
> context-{4:4}
> 4 locks held by kworker/u3:2/212:
> #0: ffff8880028c6530 ((wq_completion)hci0#2){+.+.}-{0:0}, at:
> process_one_work+0x4dc/0x9a0
> #1: ffff888001aafde0 ((work_completion)(&hdev->rx_work)){+.+.}-{0:0},
> at: process_one_work+0x4dc/0x9a0
> #2: ffff888002600070 (&hdev->lock){+.+.}-{3:3}, at:
> hci_cc_le_set_cig_params+0x64/0x4f0
> #3: ffffffffa5994b00 (rcu_read_lock){....}-{1:2}, at:
> hci_cc_le_set_cig_params+0x2f9/0x4f0
>
> [...]
Here is the summary with links:
- Bluetooth: hci_event: Fix Invalid wait context
https://git.kernel.org/bluetooth/bluetooth-next/c/fd18e1680ee2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
