From: Leon Romanovsky <leon@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Hariprasad Kelam <hkelam@marvell.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
sgoutham@marvell.com, gakula@marvell.com, sbhatta@marvell.com
Subject: Re: [net PATCH] octeontx2-pf: Fix resource leakage in VF driver unbind
Date: Tue, 10 Jan 2023 13:11:34 +0200 [thread overview]
Message-ID: <Y71H5ub5K+9GlGTm@unreal> (raw)
In-Reply-To: <79108835e679706d138afc33a19a96ed4a1f71ea.camel@redhat.com>
On Tue, Jan 10, 2023 at 11:43:28AM +0100, Paolo Abeni wrote:
> Hello,
>
> On Tue, 2023-01-10 at 12:29 +0200, Leon Romanovsky wrote:
> > On Tue, Jan 10, 2023 at 10:20:15AM +0000, patchwork-bot+netdevbpf@kernel.org wrote:
> > > Hello:
> > >
> > > This patch was applied to netdev/net.git (master)
> > > by Paolo Abeni <pabeni@redhat.com>:
> > >
> > > On Mon, 9 Jan 2023 11:43:25 +0530 you wrote:
> > > > resources allocated like mcam entries to support the Ntuple feature
> > > > and hash tables for the tc feature are not getting freed in driver
> > > > unbind. This patch fixes the issue.
> > > >
> > > > Fixes: 2da489432747 ("octeontx2-pf: devlink params support to set mcam entry count")
> > > > Signed-off-by: Hariprasad Kelam <hkelam@marvell.com>
> > > > Signed-off-by: Sunil Kovvuri Goutham <sgoutham@marvell.com>
> > > >
> > > > [...]
> > >
> > > Here is the summary with links:
> > > - [net] octeontx2-pf: Fix resource leakage in VF driver unbind
> > > https://git.kernel.org/netdev/net/c/53da7aec3298
> >
> > I don't think that this patch should be applied.
> >
> > It looks like wrong Fixes to me and I don't see clearly how structures
> > were allocated on VF which were cleared in this patch.
>
> My understanding is that the resource allocation happens via:
>
> otx2_dl_mcam_count_set()
>
> which is registered as the devlink parameter write operation on the vf
> by the fixes commit - the patch looks legit to me.
>
> Did I miss something?
No, you are right. I'm not sure if I would be able to see that OTX2_FLAG_MCAM_ENTRIES_ALLOC
flag without your hint.
Thanks
prev parent reply other threads:[~2023-01-10 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 6:13 [net PATCH] octeontx2-pf: Fix resource leakage in VF driver unbind Hariprasad Kelam
2023-01-10 9:57 ` Leon Romanovsky
2023-01-10 10:20 ` patchwork-bot+netdevbpf
2023-01-10 10:29 ` Leon Romanovsky
2023-01-10 10:43 ` Paolo Abeni
2023-01-10 11:11 ` Leon Romanovsky [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=Y71H5ub5K+9GlGTm@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--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 \
/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