From: patchwork-bot+bluetooth@kernel.org
To: Zhongqiu Han <quic_zhonhan@quicinc.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, chharry@chromium.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btusb: Fix potential NULL dereference on kmalloc failure
Date: Thu, 10 Jul 2025 17:32:46 +0000 [thread overview]
Message-ID: <175216876624.1607762.15975000995964161404.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250705105246.1383084-1-quic_zhonhan@quicinc.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 5 Jul 2025 18:52:46 +0800 you wrote:
> Avoid potential NULL pointer dereference by checking the return value of
> kmalloc and handling allocation failure properly.
>
> Fixes: 7d70989fcea7 ("Bluetooth: btusb: Add HCI Drv commands for configuring altsetting")
> Signed-off-by: Zhongqiu Han <quic_zhonhan@quicinc.com>
> ---
> drivers/bluetooth/btusb.c | 2 ++
> 1 file changed, 2 insertions(+)
Here is the summary with links:
- Bluetooth: btusb: Fix potential NULL dereference on kmalloc failure
https://git.kernel.org/bluetooth/bluetooth-next/c/982ac6d394db
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-07-10 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-05 10:52 [PATCH] Bluetooth: btusb: Fix potential NULL dereference on kmalloc failure Zhongqiu Han
2025-07-05 11:31 ` bluez.test.bot
2025-07-10 17:32 ` 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=175216876624.1607762.15975000995964161404.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chharry@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=quic_zhonhan@quicinc.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