From: patchwork-bot+bluetooth@kernel.org
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: martin.blumenstingl@googlemail.com, marcel@holtmann.org,
luiz.dentz@gmail.com, jeremy@jcline.org, hdegoede@redhat.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btrtl: Prevent potential NULL dereference
Date: Wed, 02 Apr 2025 21:10:33 +0000 [thread overview]
Message-ID: <174362823399.1678044.12965511758413449194.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <0174d93d-f3a5-48ed-a755-ed7f6455c1bf@stanley.mountain>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 2 Apr 2025 14:01:41 +0300 you wrote:
> The btrtl_initialize() function checks that rtl_load_file() either
> had an error or it loaded a zero length file. However, if it loaded
> a zero length file then the error code is not set correctly. It
> results in an error pointer vs NULL bug, followed by a NULL pointer
> dereference. This was detected by Smatch:
>
> drivers/bluetooth/btrtl.c:592 btrtl_initialize() warn: passing zero to 'ERR_PTR'
>
> [...]
Here is the summary with links:
- Bluetooth: btrtl: Prevent potential NULL dereference
https://git.kernel.org/bluetooth/bluetooth-next/c/113f1345ce0c
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-04-02 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 11:01 [PATCH] Bluetooth: btrtl: Prevent potential NULL dereference Dan Carpenter
2025-04-02 11:55 ` Hans de Goede
2025-04-02 21:10 ` 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=174362823399.1678044.12965511758413449194.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=hdegoede@redhat.com \
--cc=jeremy@jcline.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=martin.blumenstingl@googlemail.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