From: patchwork-bot+bluetooth@kernel.org
To: Chengfeng Ye <nicoyip.dev@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
padovan@profusion.mobi, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] Bluetooth: Serialize TX scheduling with teardown
Date: Mon, 28 Sep 2026 15:40:21 +0000 [thread overview]
Message-ID: <179061002143.4169639.3931590453704871029.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1790407061.git.nicoyip.dev@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 27 Sep 2026 01:04:01 +0800 you wrote:
> The TX scheduler drops its RCU read lock before using the selected channel
> or connection. Teardown on the separate request workqueue can then free
> that object while transmission is still using it.
>
> This series fixes two distinct lifetime bugs using the existing device
> mutex:
>
> [...]
Here is the summary with links:
- [net,1/2] Bluetooth: hci_core: Serialize ACL scheduling with channel deletion
https://git.kernel.org/bluetooth/bluetooth-next/c/f4845ab191a4
- [net,2/2] Bluetooth: hci_core: Serialize SCO and ISO scheduling with teardown
https://git.kernel.org/bluetooth/bluetooth-next/c/848a7a91c7f0
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:[~2026-09-28 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 17:04 [PATCH net 0/2] Bluetooth: Serialize TX scheduling with teardown Chengfeng Ye
2026-09-26 17:04 ` [PATCH net 1/2] Bluetooth: hci_core: Serialize ACL scheduling with channel deletion Chengfeng Ye
2026-09-27 23:27 ` Bluetooth: Serialize TX scheduling with teardown bluez.test.bot
2026-09-26 17:04 ` [PATCH net 2/2] Bluetooth: hci_core: Serialize SCO and ISO " Chengfeng Ye
2026-09-28 15:40 ` 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=179061002143.4169639.3931590453704871029.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=nicoyip.dev@gmail.com \
--cc=padovan@profusion.mobi \
/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.