From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: MGMT: Fix possible deadlocks
Date: Fri, 22 Nov 2024 18:30:31 +0000 [thread overview]
Message-ID: <173230023177.2761600.67535148027454591.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241121164335.3848135-1-luiz.dentz@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 21 Nov 2024 11:43:35 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This fixes possible deadlocks like the following caused by
> hci_cmd_sync_dequeue causing the destroy function to run:
>
> INFO: task kworker/u19:0:143 blocked for more than 120 seconds.
> Tainted: G W O 6.8.0-2024-03-19-intel-next-iLS-24ww14 #1
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> task:kworker/u19:0 state:D stack:0 pid:143 tgid:143 ppid:2 flags:0x00004000
> Workqueue: hci0 hci_cmd_sync_work [bluetooth]
> Call Trace:
> <TASK>
> __schedule+0x374/0xaf0
> schedule+0x3c/0xf0
> schedule_preempt_disabled+0x1c/0x30
> __mutex_lock.constprop.0+0x3ef/0x7a0
> __mutex_lock_slowpath+0x13/0x20
> mutex_lock+0x3c/0x50
> mgmt_set_connectable_complete+0xa4/0x150 [bluetooth]
> ? kfree+0x211/0x2a0
> hci_cmd_sync_dequeue+0xae/0x130 [bluetooth]
> ? __pfx_cmd_complete_rsp+0x10/0x10 [bluetooth]
> cmd_complete_rsp+0x26/0x80 [bluetooth]
> mgmt_pending_foreach+0x4d/0x70 [bluetooth]
> __mgmt_power_off+0x8d/0x180 [bluetooth]
> ? _raw_spin_unlock_irq+0x23/0x40
> hci_dev_close_sync+0x445/0x5b0 [bluetooth]
> hci_set_powered_sync+0x149/0x250 [bluetooth]
> set_powered_sync+0x24/0x60 [bluetooth]
> hci_cmd_sync_work+0x90/0x150 [bluetooth]
> process_one_work+0x13e/0x300
> worker_thread+0x2f7/0x420
> ? __pfx_worker_thread+0x10/0x10
> kthread+0x107/0x140
> ? __pfx_kthread+0x10/0x10
> ret_from_fork+0x3d/0x60
> ? __pfx_kthread+0x10/0x10
> ret_from_fork_asm+0x1b/0x30
> </TASK>
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: MGMT: Fix possible deadlocks
https://git.kernel.org/bluetooth/bluetooth-next/c/4ae007fdffc9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-11-22 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 16:43 [PATCH v1] Bluetooth: MGMT: Fix possible deadlocks Luiz Augusto von Dentz
2024-11-21 17:31 ` [v1] " bluez.test.bot
2024-11-22 9:28 ` [PATCH v1] " K, Kiran
2024-11-22 18:30 ` patchwork-bot+bluetooth [this message]
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=173230023177.2761600.67535148027454591.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.