From: patchwork-bot+netdevbpf@kernel.org
To: Dawei Feng <dawei.feng@seu.edu.cn>
Cc: kuba@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, kees@kernel.org,
Ariel.Elior@qlogic.com, Yuval.Mintz@qlogic.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] qed: fix double free in qed_cxt_tables_alloc()
Date: Thu, 21 May 2026 15:20:14 +0000 [thread overview]
Message-ID: <177937681438.379332.10701744949542256391.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260520070323.2762379-1-dawei.feng@seu.edu.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 20 May 2026 15:03:23 +0800 you wrote:
> If one of the later PF or VF CID bitmap allocations fails,
> qed_cid_map_alloc() jumps to cid_map_fail and frees the previously
> allocated CID bitmaps before returning an error. qed_cxt_tables_alloc()
> then calls qed_cxt_mngr_free(), which invokes qed_cid_map_free()
> again.
>
> Fix this by setting each CID bitmap pointer to NULL after bitmap_free()
> to avoid double free.
>
> [...]
Here is the summary with links:
- [net] qed: fix double free in qed_cxt_tables_alloc()
https://git.kernel.org/netdev/net/c/2bccfb8476ca
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-21 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 7:03 [PATCH net] qed: fix double free in qed_cxt_tables_alloc() Dawei Feng
2026-05-21 15: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=177937681438.379332.10701744949542256391.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Ariel.Elior@qlogic.com \
--cc=Yuval.Mintz@qlogic.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dawei.feng@seu.edu.cn \
--cc=edumazet@google.com \
--cc=jianhao.xu@seu.edu.cn \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox