From: patchwork-bot+netdevbpf@kernel.org
To: Harshitha Ramamurthy <hramamurthy@google.com>
Cc: netdev@vger.kernel.org, joshwash@google.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, willemb@google.com,
pkaligineedi@google.com, sdf@fomichev.me, jordanrhee@google.com,
nktgrg@google.com, shailend@google.com, horms@kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] gve: defer interrupt enabling until NAPI registration
Date: Mon, 29 Dec 2025 18:10:06 +0000 [thread overview]
Message-ID: <176703180604.3020297.10151848837603097522.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251219102945.2193617-1-hramamurthy@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 19 Dec 2025 10:29:45 +0000 you wrote:
> From: Ankit Garg <nktgrg@google.com>
>
> Currently, interrupts are automatically enabled immediately upon
> request. This allows interrupt to fire before the associated NAPI
> context is fully initialized and cause failures like below:
>
> [ 0.946369] Call Trace:
> [ 0.946369] <IRQ>
> [ 0.946369] __napi_poll+0x2a/0x1e0
> [ 0.946369] net_rx_action+0x2f9/0x3f0
> [ 0.946369] handle_softirqs+0xd6/0x2c0
> [ 0.946369] ? handle_edge_irq+0xc1/0x1b0
> [ 0.946369] __irq_exit_rcu+0xc3/0xe0
> [ 0.946369] common_interrupt+0x81/0xa0
> [ 0.946369] </IRQ>
> [ 0.946369] <TASK>
> [ 0.946369] asm_common_interrupt+0x22/0x40
> [ 0.946369] RIP: 0010:pv_native_safe_halt+0xb/0x10
>
> [...]
Here is the summary with links:
- [net] gve: defer interrupt enabling until NAPI registration
https://git.kernel.org/netdev/net/c/3d970eda0034
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-12-29 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 10:29 [PATCH net] gve: defer interrupt enabling until NAPI registration Harshitha Ramamurthy
2025-12-29 18:10 ` 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=176703180604.3020297.10151848837603097522.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=jordanrhee@google.com \
--cc=joshwash@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nktgrg@google.com \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=sdf@fomichev.me \
--cc=shailend@google.com \
--cc=stable@vger.kernel.org \
--cc=willemb@google.com \
/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).