From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: ISO: Fix possible circular locking dependency
Date: Wed, 11 Jan 2023 20:10:17 +0000 [thread overview]
Message-ID: <167346781702.28484.10748896819178620223.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230111012254.3724082-2-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 Tue, 10 Jan 2023 17:22:54 -0800 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This attempts to fix the following trace:
>
> iso-tester/52 is trying to acquire lock:
> ffff8880024e0070 (&hdev->lock){+.+.}-{3:3}, at:
> iso_sock_listen+0x29e/0x440
>
> [...]
Here is the summary with links:
- Bluetooth: ISO: Fix possible circular locking dependency
https://git.kernel.org/bluetooth/bluetooth-next/c/489691e98909
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-01-11 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 1:22 [PATCH] Bluetooth: hci_event: Fix Invalid wait context Luiz Augusto von Dentz
2023-01-11 1:22 ` [PATCH] Bluetooth: ISO: Fix possible circular locking dependency Luiz Augusto von Dentz
2023-01-11 2:37 ` bluez.test.bot
2023-01-11 20:10 ` patchwork-bot+bluetooth [this message]
2023-01-11 2:41 ` Bluetooth: hci_event: Fix Invalid wait context bluez.test.bot
2023-01-11 20:10 ` [PATCH] " patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2023-01-10 21:30 [PATCH] Bluetooth: ISO: Fix possible circular locking dependency Luiz Augusto von Dentz
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=167346781702.28484.10748896819178620223.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.