From: patchwork-bot+bluetooth@kernel.org
To: Artur <arturfaleiros1254@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, max.chou@realtek.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Bluetooth: btrtl: Don't return NULL from btrtl_initialize()
Date: Thu, 19 Nov 2026 18:50:06 +0000 [thread overview]
Message-ID: <179511420603.3743161.9291199653240239049.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261115195313.20809-1-arturfaleiros1254@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 15 Nov 2026 19:53:11 +0000 you wrote:
> btrtl_initialize() has two error paths that jump to err_free while
> 'ret' is still 0, so the function returns ERR_PTR(0), which is NULL.
> Both callers only check the result with IS_ERR() and then dereference
> the pointer.
>
> Patch 1 fixes the path taken when reading the RTL_SEC_PROJ register
> fails. It can be hit by a controller that times out or answers the
> vendor command with an error during setup.
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: btrtl: Return an error when reading the key id fails
https://git.kernel.org/bluetooth/bluetooth-next/c/c3cdaaa5cb5b
- [2/2] Bluetooth: btrtl: Set an error code when skb allocation fails
https://git.kernel.org/bluetooth/bluetooth-next/c/fc4527d1e1b6
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-19 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 19:53 Artur
2026-11-15 19:53 ` [PATCH 1/2] Bluetooth: btrtl: Return an error when reading the key id fails Artur
2026-11-15 19:53 ` [PATCH 2/2] Bluetooth: btrtl: Set an error code when skb allocation fails Artur
2026-11-19 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=179511420603.3743161.9291199653240239049.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=arturfaleiros1254@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=max.chou@realtek.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
all inboxes | Powered by JetHome®