From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: netdev@vger.kernel.org, kuba@kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
petrm@nvidia.com, willemb@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] netdevsim: fix panic when NETIF_F_LOOPBACK is set on a VF port
Date: Thu, 03 Sep 2026 01:40:53 +0000 [thread overview]
Message-ID: <178839965389.3035212.12987260351149513581.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260901061851.61734-1-jiayuan.chen@linux.dev>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 1 Sep 2026 14:18:50 +0800 you wrote:
> A netdevsim VF port cannot process incoming data. It never runs
> nsim_queue_init(), so ns->rq is NULL, and nsim_vf_netdev_ops has no
> ->ndo_open, so its NAPI is never set up either.
>
> nsim_setup() offers NETIF_F_LOOPBACK to both PF and VF ports. Turning
> it on for a VF makes nsim_start_xmit() take ns itself as peer_ns and
> dereference peer_ns->rq[], which panics.
>
> [...]
Here is the summary with links:
- [net,v2] netdevsim: fix panic when NETIF_F_LOOPBACK is set on a VF port
https://git.kernel.org/netdev/net-next/c/5add7c8d59fa
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:[~2026-09-03 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 6:18 [PATCH net v2] netdevsim: fix panic when NETIF_F_LOOPBACK is set on a VF port Jiayuan Chen
2026-09-03 1:40 ` 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=178839965389.3035212.12987260351149513581.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=jiayuan.chen@linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.