From: Markus Elfring <Markus.Elfring@web.de>
To: Su Hui <suhui@nfschina.com>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
Bill Wendling <morbo@google.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Geethasowjanya Akula <gakula@marvell.com>,
Hariprasad Kelam <hkelam@marvell.com>,
Jakub Kicinski <kuba@kernel.org>,
Jerin Jacob <jerinj@marvell.com>,
Justin Stitt <justinstitt@google.com>,
Kalesh Anakkur Purayil <kalesh-anakkur.purayil@broadcom.com>,
Linu Cherian <lcherian@marvell.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Subbaraya Sundeep Bhatta <sbhatta@marvell.com>,
Sunil Kovvuri Goutham <sgoutham@marvell.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
llvm@lists.linux.dev, Suman Ghosh <sumang@marvell.com>
Subject: Re: [PATCH net] octeontx2-af: fix the double free in rvu_npc_freemem()
Date: Wed, 24 Apr 2024 09:56:11 +0200 [thread overview]
Message-ID: <7ed5b3e0-933a-4a6c-a07c-3cdc8a9cc680@web.de> (raw)
In-Reply-To: <20240424022724.144587-1-suhui@nfschina.com>
…
> npc_mcam_rsrcs_deinit() has released 'mcam->counters.bmap'. Deleted this
> redundant kfree() to fix this double free problem.
…
Can a wording variant (like the following) be a bit nicer?
The object “mcam->counters.bmap” was released during the execution of
the function “npc_mcam_rsrcs_deinit”.
Delete a subsequent kfree() call to fix this double free problem.
Regards,
Markus
next prev parent reply other threads:[~2024-04-24 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 2:27 [PATCH net] octeontx2-af: fix the double free in rvu_npc_freemem() Su Hui
2024-04-24 4:05 ` [EXTERNAL] " Geethasowjanya Akula
2024-04-24 4:05 ` Kalesh Anakkur Purayil
2024-04-24 4:57 ` ] " Hariprasad Kelam
2024-04-24 7:56 ` Markus Elfring [this message]
2024-04-25 15:40 ` patchwork-bot+netdevbpf
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=7ed5b3e0-933a-4a6c-a07c-3cdc8a9cc680@web.de \
--to=markus.elfring@web.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=justinstitt@google.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=suhui@nfschina.com \
--cc=sumang@marvell.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