From: Simon Horman <horms@kernel.org>
To: netdev-bot+sashiko@kernel.org
Cc: vulab@iscas.ac.cn, idosch@nvidia.com, petrm@nvidia.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] mlxsw: spectrum_ptp: release parsing depth on MTPPPC write failure
Date: Mon, 9 Nov 2026 13:22:26 +0000 [thread overview]
Message-ID: <20261109132226.GL18859@horms.kernel.org> (raw)
In-Reply-To: <179405323723.994134.11947248661617076904@kernel.org>
On Sat, Nov 07, 2026 at 12:07:17PM +0000, netdev-bot+sashiko@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential
> issue(s) to consider.
>
> Critical: 0 · High: 1 (1) · Medium: 0 · Low: 0 (1)
>
> If you believe none of the issues are legitimate, please reply to each
> issue of Medium severity or higher and explain why the AI is wrong.
> If any of them are legitimate and you plan to respin, please let patchwork
> know by including "pw-bot: cr" as a separate line at the end of your reply
> (one such reply per series is enough).
>
> - [High] The patch fixes the enable-path leak but adds the same leak on
> the port-removal path.
I believe the issue flagged here is pre-existing. While it does affect this
patch, the patch is still an improvement in its own right. I would
therefore ask for follow-up on the concurrency concern raised here, but I
do not think it should block progress of this patch.
And while the separate bot email, requesting information on how
the problem was found, should be answered, overall this looks good to me.
Reviewed-by: Simon Horman <horms@kernel.org>
>
> Pre-existing issues:
> - [High] This problem wasn't introduced by this patch, but
> mlxsw_sp1_ptp_mtpppc_update() has no serialization between its two…
> - [Low] The new rollback in mlxsw_sp1_ptp_mtpppc_update()
> (spectrum_ptp.c:1223-1226) calls mlxsw_sp_parsing_depth_dec().
...
prev parent reply other threads:[~2026-11-09 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 10:28 Wentao Liang
2026-11-03 10:33 ` netdev-bot+sinfo
2026-11-03 10:40 ` Krzysztof Kozlowski
2026-11-03 11:11 ` Krzysztof Kozlowski
2026-11-07 12:07 ` netdev-bot+sashiko
2026-11-09 13:22 ` Simon Horman [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=20261109132226.GL18859@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.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
all inboxes | Powered by JetHome®