From: patchwork-bot+netdevbpf@kernel.org
To: Gaurav Kohli <gauravkohli@linux.microsoft.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, wei.liu@kernel.org, decui@microsoft.com,
linux-hyperv@vger.kernel.org, netdev@vger.kernel.org,
kuba@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 net] hv_netvsc: Fix race between VF offering and VF association message from host
Date: Fri, 07 Oct 2022 07:50:16 +0000 [thread overview]
Message-ID: <166512901611.847.9066991883848590032.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1665035579-13755-2-git-send-email-gauravkohli@linux.microsoft.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 5 Oct 2022 22:52:59 -0700 you wrote:
> 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@vger.kernel.org
> Fixes: 00d7ddba11436 ("hv_netvsc: pair VF based on serial number")
> Reviewed-by: Haiyang Zhang <haiyangz@microsoft.com>
> Signed-off-by: Gaurav Kohli <gauravkohli@linux.microsoft.com>
>
> [...]
Here is the summary with links:
- [v2,net] hv_netvsc: Fix race between VF offering and VF association message from host
https://git.kernel.org/netdev/net/c/365e1ececb29
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-10-07 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 5:52 [PATCH v2 net] hv_netvsc: Fix race between VF offering and VF association message from host Gaurav Kohli
2022-10-06 5:52 ` Gaurav Kohli
2022-10-07 7:50 ` patchwork-bot+netdevbpf [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=166512901611.847.9066991883848590032.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=decui@microsoft.com \
--cc=gauravkohli@linux.microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@kernel.org \
/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