From: patchwork-bot+bluetooth@kernel.org
To: Calvin Owens <calvin@wbinvd.org>
Cc: linux-kernel@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, sean.wang@mediatek.com,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
amitkumar.karwar@nxp.com, neeraj.sanjaykale@nxp.com,
yang.li@amlogic.com, pmenzel@molgen.mpg.de,
linux-bluetooth@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, francesco@valla.it
Subject: Re: [PATCH] Bluetooth: fix corruption in h4_recv_buf() after cleanup
Date: Thu, 23 Oct 2025 21:40:07 +0000 [thread overview]
Message-ID: <176125560702.3260295.10385824633115850837.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ab6fa50055fa0c39e5501c123c36e662eb48ae61.1761245114.git.calvin@wbinvd.org>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 23 Oct 2025 11:47:19 -0700 you wrote:
> Thanks to Francesco Valla's investigation, the reason for the duplicate
> code I recently cleaned up is finally clear: a different structure is
> stored in drvdata for the drivers which used that duplicate function,
> but h4_recv_buf() assumes drvdata is always an hci_uart structure.
>
> Consequently, alignment and padding are now randomly corrupted for
> btmtkuart, btnxpuart, and bpa10x in h4_recv_buf(), causing erratic
> breakage.
>
> [...]
Here is the summary with links:
- Bluetooth: fix corruption in h4_recv_buf() after cleanup
https://git.kernel.org/bluetooth/bluetooth-next/c/1aaa18cc80c5
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:[~2025-10-23 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 18:47 [PATCH] Bluetooth: fix corruption in h4_recv_buf() after cleanup Calvin Owens
2025-10-23 21: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=176125560702.3260295.10385824633115850837.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=amitkumar.karwar@nxp.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=calvin@wbinvd.org \
--cc=francesco@valla.it \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=matthias.bgg@gmail.com \
--cc=neeraj.sanjaykale@nxp.com \
--cc=pmenzel@molgen.mpg.de \
--cc=sean.wang@mediatek.com \
--cc=yang.li@amlogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox