[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165705781323.1977.3304816866885746199.git-patchwork-notify@kernel.org>
Date: Tue, 05 Jul 2022 21:50:13 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Vasyl Vavrychuk <vasyl.vavrychuk@...nsynergy.com>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-bluetooth@...r.kernel.org, max.oss.09@...il.com,
francesco.dolcini@...adex.com, mat.jonczyk@...pl, kuba@...nel.org,
marcel@...tmann.org, max.krummenacher@...adex.com,
johan.hedberg@...il.com, luiz.dentz@...il.com, davem@...emloft.net,
pabeni@...hat.com, edumazet@...gle.com
Subject: Re: [PATCH] Bluetooth: core: Fix deadlock due to
`cancel_work_sync(&hdev->power_on)` from hci_power_on_sync.
Hello:
This patch was applied to netdev/net.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@...el.com>:
On Tue, 5 Jul 2022 15:59:31 +0300 you wrote:
> `cancel_work_sync(&hdev->power_on)` was moved to hci_dev_close_sync in
> commit [1] to ensure that power_on work is canceled after HCI interface
> down.
>
> But, in certain cases power_on work function may call hci_dev_close_sync
> itself: hci_power_on -> hci_dev_do_close -> hci_dev_close_sync ->
> cancel_work_sync(&hdev->power_on), causing deadlock. In particular, this
> happens when device is rfkilled on boot. To avoid deadlock, move
> power_on work canceling out of hci_dev_do_close/hci_dev_close_sync.
>
> [...]
Here is the summary with links:
- Bluetooth: core: Fix deadlock due to `cancel_work_sync(&hdev->power_on)` from hci_power_on_sync.
https://git.kernel.org/netdev/net/c/e36bea6e78ab
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists