Re: [PATCH net V2] net/mlx5e: rep, Fix races between devcom PAIR event and uplink close

[Shay Drory <shayd@nvidia.com>]

On 13/11/2026 17:27, netdev-bot+sinfo@kernel.org wrote:
> Hi!
>
> This is an automated message. This series looks like a fix, but its
> commit messages seem to be missing some information:
>
>  - How the issue was discovered, e.g. hit in production, hit during
>    development, syzbot report, manual code inspection, LLM or static
>    analysis tool scan.
>
>  - Whether the issue was actually triggered, or is only theoretical
>    (e.g. found by LLM and not proven at runtime). If it was triggered
>    please include the symptoms, like the stack trace or kernel messages.
>
> Please do not repost the series just to address the above. Instead,
> reply to this email with the missing information, so that reviewers
> can take it into account. If the series needs another revision for
> other reasons, please include the information in the commit messages
> then.
>
> The evaluation is done by an LLM so it may be wrong, if you think
> that is the case please reply and explain.

Hi,

The issue was observed during OS boot, while a boot script moved the PFs
to switchdev mode. It reproduces by bringing one PF uplink down/up
(mlx5e_sqs2vport_stop()) while the peer PF toggles legacy <-> switchdev
(devcom PAIR/UNPAIR).