Re: [PATCH net-next v2 2/5] hv_netvsc: hold the VF's instance lock when installing XDP on it

[netdev-bot+sashiko@kernel.org]

Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.

Low priority / nit picks for your consideration:

- [Low] The stable Cc trailer contradicts the rest of the commit
  "hv_netvsc: hold the VF's instance lock when installing XDP on it".

--

hv_netvsc: hold the VF's instance lock when installing XDP on it

netvsc_bpf() runs with only RTNL held, so the VF's ndo_bpf() is called
without the VF's instance lock. That trips the lockdep assertion in
dev_get_min_mp_channel_count() and can race with memory provider binding.
This patch takes the VF's ops lock around netvsc_vf_setxdp() in
netvsc_bpf(), and adds an assertion in netvsc_vf_setxdp().

> Reported by Sashiko during core rework, the race was not reproduced.
>
> Cc: stable+noautosel@kernel.org # LLM report + LLM fix, untested
> Fixes: 3ec523304976 ("hv_netvsc: fix potential deadlock in netvsc_vf_setxdp()")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> Tested-by: Kameron Carr <kameroncarr@linux.microsoft.com>
> Tested-by: Erni Sri Satya Vennela <ernis@linux.microsoft.com>

[Severity: Low]
This isn't a bug, but the stable trailer still says "untested". The same
commit carries two Tested-by: tags.

The v2 changelog says:

> v2:
>  - commit msg: say that the race was not reproduced, rather than that
>    the fix is untested, as functional testing covered it

The body was updated to say "the race was not reproduced". The comment on
the Cc: stable+noautosel trailer, which stable maintainers read when they
decide on the backport, was not changed.

Should the trailer be updated to match, for example to something like
"LLM report + LLM fix, race not reproduced"?

-- 
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261109194843.1353592-1-kuba%40kernel.org