From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: L2CAP: Fix corrupted list in hci_chan_del
Date: Fri, 07 Feb 2025 21:10:38 +0000 [thread overview]
Message-ID: <173896263850.2382953.5014769464223738334.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250207201727.3449504-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 Fri, 7 Feb 2025 15:17:27 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This fixes the following trace by reworking the locking of l2cap_conn
> so instead of only locking when changing the chan_l list this promotes
> chan_lock to a general lock of l2cap_conn so whenever it is being held
> it would prevents the likes of l2cap_conn_del to run:
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: L2CAP: Fix corrupted list in hci_chan_del
https://git.kernel.org/bluetooth/bluetooth-next/c/dd6367916d2d
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:[~2025-02-07 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 20:17 [PATCH v2] Bluetooth: L2CAP: Fix corrupted list in hci_chan_del Luiz Augusto von Dentz
2025-02-07 20:55 ` [v2] " bluez.test.bot
2025-02-07 21:10 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-07 21:01 [PATCH v2] " Luiz Augusto von Dentz
2025-02-07 21:10 ` patchwork-bot+bluetooth
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=173896263850.2382953.5014769464223738334.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.