From: patchwork-bot+netdevbpf@kernel.org
To: Dawei Feng <dawei.feng@seu.edu.cn>
Cc: sgoutham@marvell.com, gakula@marvell.com, sbhatta@marvell.com,
hkelam@marvell.com, bbhushan2@marvell.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, jianhao.xu@seu.edu.cn,
stable@vger.kernel.org, zilin@seu.edu.cn
Subject: Re: [PATCH net] octeontx2-pf: fix double free in rvu_rep_rsrc_init()
Date: Fri, 15 May 2026 01:20:05 +0000 [thread overview]
Message-ID: <177880800580.150313.8207368814594738900.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260513151320.213260-1-dawei.feng@seu.edu.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 13 May 2026 23:13:20 +0800 you wrote:
> rvu_rep_rsrc_init() allocates queue memory before calling
> otx2_init_hw_resources(). When hardware resource setup fails,
> otx2_init_hw_resources() already unwinds the partially initialized
> SQ, CQ, and aura state before returning an error. The representor
> error path then calls otx2_free_hw_resources() again and can free
> the same resources a second time.
>
> [...]
Here is the summary with links:
- [net] octeontx2-pf: fix double free in rvu_rep_rsrc_init()
https://git.kernel.org/netdev/net/c/e8fb3de2a8ef
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-05-15 1:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 15:13 [PATCH net] octeontx2-pf: fix double free in rvu_rep_rsrc_init() Dawei Feng
2026-05-14 5:05 ` [EXTERNAL] " Geethasowjanya Akula
2026-05-15 1:20 ` 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=177880800580.150313.8207368814594738900.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=dawei.feng@seu.edu.cn \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jianhao.xu@seu.edu.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=stable@vger.kernel.org \
--cc=zilin@seu.edu.cn \
/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.