From: patchwork-bot+netdevbpf@kernel.org
To: Dipayaan Roy <dipayanroy@linux.microsoft.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
linux-hyperv@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, dipayanroy@micorsoft.com,
ssengar@linux.microsoft.com
Subject: Re: [PATCH net] net: hv_netvsc: fix loss of early receive events from host during channel open.
Date: Wed, 27 Aug 2025 01:30:06 +0000 [thread overview]
Message-ID: <175625820626.162890.13956078628306112530.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250825115627.GA32189@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 25 Aug 2025 04:56:27 -0700 you wrote:
> The hv_netvsc driver currently enables NAPI after opening the primary and
> subchannels. This ordering creates a race: if the Hyper-V host places data
> in the host -> guest ring buffer and signals the channel before
> napi_enable() has been called, the channel callback will run but
> napi_schedule_prep() will return false. As a result, the NAPI poller never
> gets scheduled, the data in the ring buffer is not consumed, and the
> receive queue may remain permanently stuck until another interrupt happens
> to arrive.
>
> [...]
Here is the summary with links:
- [net] net: hv_netvsc: fix loss of early receive events from host during channel open.
https://git.kernel.org/netdev/net/c/9448ccd85336
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:[~2025-08-27 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 11:56 [PATCH net] net: hv_netvsc: fix loss of early receive events from host during channel open Dipayaan Roy
2025-08-27 1:30 ` 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=175625820626.162890.13956078628306112530.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=dipayanroy@linux.microsoft.com \
--cc=dipayanroy@micorsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ssengar@linux.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;
as well as URLs for NNTP newsgroup(s).