From: patchwork-bot+bluetooth@kernel.org
To: Zhao Li <enderaoelyther@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, robh@kernel.org,
sre@kernel.org, pavel@ucw.cz, me@michaelmcallister.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_serdev: serialize flush with transmit work
Date: Tue, 17 Nov 2026 18:50:16 +0000 [thread overview]
Message-ID: <179494141677.761488.12705162409776237119.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261116080538.66575-1-enderaoelyther@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 16 Nov 2026 16:05:38 +0800 you wrote:
> hci_uart_flush() runs on HCI close and reset and frees hu->tx_skb while
> write_work may still be sending the same partial frame. The worker can
> then resume with a freed skb, or both paths can free the frame.
>
> The tty flush has stopped write_work before freeing the partial frame
> since commit 1b0d946d6f08 ("Bluetooth: hci_uart: clear HCI_UART_SENDING
> when write_work is canceled"). Do the same in the serdev flush: disable
> and drain write_work before releasing the frame, and hold
> HCI_UART_SENDING meanwhile so that hci_uart_tx_wakeup() only records
> HCI_UART_TX_WAKEUP. Then re-enable the work, release SENDING and replay
> a wakeup that arrived in between.
>
> [...]
Here is the summary with links:
- Bluetooth: hci_serdev: serialize flush with transmit work
https://git.kernel.org/bluetooth/bluetooth-next/c/ee43bade37c4
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-11-17 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 8:05 Zhao Li
2026-11-17 18:50 ` 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=179494141677.761488.12705162409776237119.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=enderaoelyther@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=me@michaelmcallister.org \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
/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®