From: patchwork-bot+bluetooth@kernel.org
To: Weiming Shi <bestswngs@gmail.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, abhishekpandit@chromium.org,
mmandlik@google.com,
syzbot+b170dbf55520ebf5969a@syzkaller.appspotmail.com,
abysamross@gmail.com, tristan@talencesecurity.com, xmei5@asu.edu
Subject: Re: [PATCH v3 bluetooth] Bluetooth: coredump: Quiesce dump work on unregister
Date: Tue, 08 Sep 2026 16:30:08 +0000 [thread overview]
Message-ID: <178888500873.3627954.10684835097412320189.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260906154332.763402-1-bestswngs@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 6 Sep 2026 23:43:32 +0800 you wrote:
> hci_devcd_handle_pkt_init() arms dump_timeout and coredump producers
> queue dump_rx without holding an hdev reference. Unregister leaves both
> works live, so disconnecting during an active dump lets them access hdev
> after hci_release_dev() frees it.
>
> Shut down coredump processing during unregister. Close the producer gate
> under dump_q.lock before disabling both works, then free the active buffer
> and queued packets under hci_dev_lock. Serializing the gate with enqueue
> prevents controller-specific workers from adding packets after the final
> purge.
>
> [...]
Here is the summary with links:
- [v3] Bluetooth: coredump: Quiesce dump work on unregister
https://git.kernel.org/bluetooth/bluetooth-next/c/701ca71884b3
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-08 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 15:43 Weiming Shi
2026-09-08 16: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=178888500873.3627954.10684835097412320189.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=abhishekpandit@chromium.org \
--cc=abysamross@gmail.com \
--cc=bestswngs@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mmandlik@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+b170dbf55520ebf5969a@syzkaller.appspotmail.com \
--cc=tristan@talencesecurity.com \
--cc=xmei5@asu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®