[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <502727b0ad4a9bc34afb421d465646248c69f7d4.camel@linux.ibm.com>
Date: Thu, 04 Dec 2025 10:48:16 +0100
From: Gerd Bayer <gbayer@...ux.ibm.com>
To: Moshe Shemesh <moshe@...dia.com>, Saeed Mahameed <saeedm@...dia.com>,
Leon Romanovsky <leon@...nel.org>, Tariq Toukan <tariqt@...dia.com>,
Mark
Bloch <mbloch@...dia.com>, Andrew Lunn <andrew+netdev@...n.ch>,
"David S.
Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub
Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Shay Drory
<shayd@...dia.com>,
Simon Horman <horms@...nel.org>
Cc: Lukas Wunner <lukas@...ner.de>, Bjorn Helgaas <helgaas@...nel.org>,
Niklas Schnelle <schnelle@...ux.ibm.com>,
Farhan Ali <alifm@...ux.ibm.com>, netdev@...r.kernel.org,
linux-rdma@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-s390@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH net] net/mlx5: Fix double unregister of HCA_PORTS
component
On Wed, 2025-12-03 at 17:14 +0200, Moshe Shemesh wrote:
>
> On 12/2/2025 1:12 PM, Gerd Bayer wrote:
> >
[ ... snip ... ]
> >
> > Fixes: 5a977b5833b7 ("net/mlx5: Lag, move devcom registration to LAG layer")
> > Signed-off-by: Gerd Bayer <gbayer@...ux.ibm.com>
>
> Reviewed-by: Moshe Shemesh <moshe@...dia.com>> ---
> > Hi Shay et al,
> >
>
> Hi Gerd,
> I stepped on this bug recently too, without s390 and was about to
> submit same fix :) So as you wrote it is unrelated to Lukas' patches and
> this fix is correct.
Good to hear. I wonder if you could share how you got to run into this?
>
> >
> > I've spotted two additional places where the devcom reference is not
> > cleared after calling mlx5_devcom_unregister_component() in
> > drivers/net/ethernet/mellanox/mlx5/core/lib/sd.c that I have not
> > addressed with a patch, since I'm unclear about how to test these
> > paths.
>
> As for the other cases, we had the patch 664f76be38a1 ("net/mlx5: Fix
> IPsec cleanup over MPV device") and two other cases on shared clock and
> SD but I don't see any flow the shared clock or SD can fail,
> specifically mlx5_sd_cleanup() checks sd pointer at beginning of the
> function and nullify it right after sd_unregister() that free devcom.
I didn't locate any calls to mxl5_devcom_unregister_component() in
"shared clock" - is that not yet upstream?
Regarding SD, I follow that sd_cleanup() is followed immediately after
sd_unregister() and does the clean-up. One path remains uncovered
though: The error exit at
https://elixir.bootlin.com/linux/v6.18/source/drivers/net/ethernet/mellanox/mlx5/core/lib/sd.c#L265
Not sure, how likely that is...
Thanks,
Gerd
Powered by blists - more mailing lists