From: alexious@zju.edu.cn
To: "Simon Horman" <horms@kernel.org>
Cc: "Edward Cree" <ecree.xilinx@gmail.com>,
"Martin Habets" <habetsm.xilinx@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-net-drivers@amd.com,
linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH] sfc: fix a double-free bug in efx_probe_filters
Date: Thu, 21 Dec 2023 01:30:59 +0800 (GMT+08:00) [thread overview]
Message-ID: <310b8095.47cb8.18c8847dbe3.Coremail.alexious@zju.edu.cn> (raw)
In-Reply-To: <20231216155145.GN6288@kernel.org>
> On Thu, Dec 14, 2023 at 11:22:46PM +0800, Zhipeng Lu wrote:
> > In efx_probe_filters, the channel->rps_flow_id is freed in a
> > efx_for_each_channel marco when success equals to 0.
> > However, after the following call chain:
> >
> > efx_probe_filters
> > |-> ef100_net_open
> > |-> ef100_net_stop
> > |-> efx_remove_filters
>
> I think the call chain may be a bit more like:
>
> ef100_net_open
> |-> efx_probe_filters
> |-> ef100_net_stop
> |-> efx_remove_filters
>
> >
> > The channel->rps_flow_id is freed again in the efx_for_each_channel of
> > efx_remove_filters, triggering a double-free bug.
> >
> > Fixes: a9dc3d5612ce ("sfc_ef100: RX filter table management and related gubbins")
> > Signed-off-by: Zhipeng Lu <alexious@zju.edu.cn>
>
> The above nit not withstanding, I agree with your reasoning.
> And that the problem was introduced in the cited commit.
>
> Reviewed-by: Simon Horman <horms@kernel.org>
Sorry for the call-chain's problem, I was not familiar with it at that time.
Thanks for Simon's correction. Appreciate!
I'll soon send a v2 patch with the corrected call-chain and RB tags.
next prev parent reply other threads:[~2023-12-20 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 15:22 [PATCH] sfc: fix a double-free bug in efx_probe_filters Zhipeng Lu
2023-12-16 15:51 ` Simon Horman
2023-12-20 17:30 ` alexious [this message]
2023-12-19 9:19 ` Paolo Abeni
2023-12-20 17:09 ` Edward Cree
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=310b8095.47cb8.18c8847dbe3.Coremail.alexious@zju.edu.cn \
--to=alexious@zju.edu.cn \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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