From: Simon Horman <horms@kernel.org>
To: Shitalkumar Gandhi <shital.gandhi45@gmail.com>
Cc: ajay.kathat@microchip.com, claudiu.beznea@tuxon.dev,
kvalo@kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Shitalkumar Gandhi <shitalkumar.gandhi@cambiumnetworks.com>
Subject: Re: [PATCH v2 v2] wifi: wilc1000: fix dma_buffer leak on bus acquire failure
Date: Fri, 15 May 2026 18:15:27 +0100 [thread overview]
Message-ID: <20260515171527.GH227382@horms.kernel.org> (raw)
In-Reply-To: <20260511042732.998311-1-shitalkumar.gandhi@cambiumnetworks.com>
On Mon, May 11, 2026 at 09:57:32AM +0530, Shitalkumar Gandhi wrote:
> wilc_wlan_firmware_download() allocates dma_buffer with kmalloc() at
> the top of the function and uses a 'fail:' label to free it via
> kfree(dma_buffer) on error.
>
> All later error paths correctly use 'goto fail' to route through this
> cleanup. However, the early failure path after the first acquire_bus()
> call uses a bare 'return ret;', which leaks dma_buffer whenever the bus
> acquire fails.
>
> Replace the early return with goto fail so the existing cleanup path
> runs.
>
> Found via a custom Coccinelle semantic patch hunting for kmalloc'd
> locals leaked on early-return error paths in driver firmware-download
> code.
>
> Fixes: 1241c5650ff7 ("wifi: wilc1000: Fill in missing error handling")
> Signed-off-by: Shitalkumar Gandhi <shitalkumar.gandhi@cambiumnetworks.com>
> ---
> Changes since v1:
> - Corrected From: and Signed-off-by: to author's real identity
> (Shitalkumar Gandhi <shitalkumar.gandhi@cambiumnetworks.com>).
> v1 was sent with incorrect author attribution due to a local
> git config mistake. No code changes.
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2026-05-15 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 11:25 [PATCH] wifi: wilc1000: fix dma_buffer leak on bus acquire failure Shitalkumar Gandhi
2026-05-11 4:27 ` [PATCH v2 v2] " Shitalkumar Gandhi
2026-05-15 17:15 ` Simon Horman [this message]
2026-05-11 4:32 ` [PATCH] " Shitalkumar Gandhi
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=20260515171527.GH227382@horms.kernel.org \
--to=horms@kernel.org \
--cc=ajay.kathat@microchip.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shital.gandhi45@gmail.com \
--cc=shitalkumar.gandhi@cambiumnetworks.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