From: patchwork-bot+bluetooth@kernel.org
To: Anas Iqbal <mohd.abd.6602@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, marcel@holtmann.org, pmenzel@molgen.mpg.de
Subject: Re: [PATCH v2] Bluetooth: hci_ll: Fix firmware leak on error path
Date: Wed, 18 Mar 2026 16:40:05 +0000 [thread overview]
Message-ID: <177385200529.385489.1830323325105295294.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260315105138.1693-1-mohd.abd.6602@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 15 Mar 2026 10:51:37 +0000 you wrote:
> Smatch reports:
>
> drivers/bluetooth/hci_ll.c:587 download_firmware() warn:
> 'fw' from request_firmware() not released on lines: 544.
>
> In download_firmware(), if request_firmware() succeeds but the returned
> firmware content is invalid (no data or zero size), the function returns
> without releasing the firmware, resulting in a resource leak.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: hci_ll: Fix firmware leak on error path
https://git.kernel.org/bluetooth/bluetooth-next/c/0f1a322270bb
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-03-18 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 16:56 [PATCH] Bluetooth: hci_ll: Fix firmware leak on error path Anas Iqbal
2026-03-14 18:13 ` bluez.test.bot
2026-03-15 8:54 ` [PATCH] " Paul Menzel
2026-03-15 10:51 ` [PATCH v2] " Anas Iqbal
2026-03-15 11:18 ` [v2] " bluez.test.bot
2026-03-18 16: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=177385200529.385489.1830323325105295294.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mohd.abd.6602@gmail.com \
--cc=pmenzel@molgen.mpg.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.