The policy of network development is to not copy the stable list. Instead the netdev maintainers want to curate the patches going to stable.
-----Original Message-----
From: Haiyang Zhang <haiyangz@xxxxxxxxxxxxx>
Sent: Thursday, September 29, 2022 1:40 PM
To: Gaurav Kohli <gauravkohli@xxxxxxxxxxxxxxxxxxx>; KY Srinivasan <kys@xxxxxxxxxxxxx>; Stephen Hemminger <sthemmin@xxxxxxxxxxxxx>; wei.liu@xxxxxxxxxx; Dexuan Cui <decui@xxxxxxxxxxxxx>; linux-hyperv@xxxxxxxxxxxxxxx; netdev@xxxxxxxxxxxxxxx
Cc: stable@xxxxxxxxxxxxxxx
Subject: RE: [PATCH net] hv_netvsc: Fix race between VF offering and VF association message from host
> -----Original Message-----
> From: Gaurav Kohli <gauravkohli@xxxxxxxxxxxxxxxxxxx>
> Sent: Wednesday, September 28, 2022 9:49 AM
> To: KY Srinivasan <kys@xxxxxxxxxxxxx>; Haiyang Zhang
> <haiyangz@xxxxxxxxxxxxx>; Stephen Hemminger
> <sthemmin@xxxxxxxxxxxxx>; wei.liu@xxxxxxxxxx; Dexuan Cui
> <decui@xxxxxxxxxxxxx>; linux-hyperv@xxxxxxxxxxxxxxx;
> netdev@xxxxxxxxxxxxxxx
> Subject: [PATCH net] hv_netvsc: Fix race between VF offering and VF
> association message from host
>
> During vm boot, there might be possibility that vf registration
> call comes before the vf association from host to vm.
>
> And this might break netvsc vf path, To prevent the same block
> vf registration until vf bind message comes from host.
>
> Cc: stable@xxxxxxxxxxxxxxx
> Fixes: 00d7ddba11436 ("hv_netvsc: pair VF based on serial number")
> Signed-off-by: Gaurav Kohli <gauravkohli@xxxxxxxxxxxxxxxxxxx>
Reviewed-by: Haiyang Zhang <haiyangz@xxxxxxxxxxxxx>
By the way, did you use "git send-email"? I didn't see the stable@xxxxxxxxxxxxxxx cc-ed in your original email.
