Message ID | 20221027145850.41806-1-tim.gardner@canonical.com |
---|---|
Headers | show |
Series | Azure: hv_netvsc: Fix race between VF offering and VF association message from host | expand |
Acked-by: Bartlomiej Zolnierkiewicz <bartlomiej.zolnierkiewicz@canonical.com> On Thu, Oct 27, 2022 at 5:00 PM Tim Gardner <tim.gardner@canonical.com> wrote: > > BugLink: https://bugs.launchpad.net/bugs/1994974 > > SRU Justification > > [Impact] > > 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, this is in order to prevent the same > block vf registration until vf bind message comes from host. > > [Test Plan] > > Microsoft tested > > [Where things could go wrong] > > The 5.4 backport patch could hang waiting for a VF addition to complete. > > [Other Info] > > SF: #00347129
On 10/27/22 8:58 AM, Tim Gardner wrote: > BugLink: https://bugs.launchpad.net/bugs/1994974 > > SRU Justification > > [Impact] > > 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, this is in order to prevent the same > block vf registration until vf bind message comes from host. > > [Test Plan] > > Microsoft tested > > [Where things could go wrong] > > The 5.4 backport patch could hang waiting for a VF addition to complete. > > [Other Info] > > SF: #00347129 > Applied to f/j/k linux-azure/master-next. Thanks. -rtg