From: patchwork-bot+netdevbpf@kernel.org
To: Bhargava Marreddy <bhargava.marreddy@broadcom.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
vsrama-krishna.nemani@broadcom.com, vikas.gupta@broadcom.com,
dharmender.garg@broadcom.com, rajashekar.hudumula@broadcom.com
Subject: Re: [PATCH net] bnge: Fix resource leak in bnge_init_nic() error path
Date: Thu, 06 Aug 2026 16:50:31 +0000 [thread overview]
Message-ID: <178603503113.1375455.14546971587248050913.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260805094022.15487-1-bhargava.marreddy@broadcom.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 5 Aug 2026 15:10:22 +0530 you wrote:
> If bnge_init_chip() fails, bnge_init_nic() jumps to err_free_ring_grps
> and returns immediately, skipping cleanup for RX ring pair buffers.
>
> Remove the early return so execution falls through to
> err_free_rx_ring_pair_bufs to properly free resources on error.
>
> Fixes: 23df6aebf803 ("bng_en: Allocate stat contexts")
> Signed-off-by: Bhargava Marreddy <bhargava.marreddy@broadcom.com>
> Reviewed-by: Dharmender Garg <dharmender.garg@broadcom.com>
> Reviewed-by: Rajashekar Hudumula <rajashekar.hudumula@broadcom.com>
>
> [...]
Here is the summary with links:
- [net] bnge: Fix resource leak in bnge_init_nic() error path
https://git.kernel.org/netdev/net/c/bfec39ff1484
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-08-06 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 9:40 [PATCH net] bnge: Fix resource leak in bnge_init_nic() error path Bhargava Marreddy
2026-08-06 16:50 ` 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=178603503113.1375455.14546971587248050913.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bhargava.marreddy@broadcom.com \
--cc=davem@davemloft.net \
--cc=dharmender.garg@broadcom.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=rajashekar.hudumula@broadcom.com \
--cc=vikas.gupta@broadcom.com \
--cc=vsrama-krishna.nemani@broadcom.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