From: patchwork-bot+netdevbpf@kernel.org
To: Abdun Nihaal <abdun.nihaal@gmail.com>
Cc: bharat@chelsio.com, horms@kernel.org, Markus.Elfring@web.de,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, rahul.lakkireddy@chelsio.com,
vishal@chelsio.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net] cxgb4: fix memory leak in cxgb4_init_ethtool_filters() error path
Date: Thu, 17 Apr 2025 01:00:34 +0000 [thread overview]
Message-ID: <174485163427.3551658.3881939557825987516.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250414170649.89156-1-abdun.nihaal@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 14 Apr 2025 22:36:46 +0530 you wrote:
> In the for loop used to allocate the loc_array and bmap for each port, a
> memory leak is possible when the allocation for loc_array succeeds,
> but the allocation for bmap fails. This is because when the control flow
> goes to the label free_eth_finfo, only the allocations starting from
> (i-1)th iteration are freed.
>
> Fix that by freeing the loc_array in the bmap allocation error path.
>
> [...]
Here is the summary with links:
- [v2,net] cxgb4: fix memory leak in cxgb4_init_ethtool_filters() error path
https://git.kernel.org/netdev/net/c/00ffb3724ce7
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-17 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 17:06 [PATCH v2 net] cxgb4: fix memory leak in cxgb4_init_ethtool_filters() error path Abdun Nihaal
2025-04-16 20:08 ` Jacob Keller
2025-04-17 1:00 ` patchwork-bot+netdevbpf [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=174485163427.3551658.3881939557825987516.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=abdun.nihaal@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=bharat@chelsio.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=vishal@chelsio.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