From: Jakub Slepecki <jakub.slepecki@intel.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
<nxne.cnse.osdt.itp.upstreaming@intel.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next] ice: fix broken Rx on VFs
Date: Tue, 25 Nov 2025 11:59:05 +0100 [thread overview]
Message-ID: <159bb793-508c-42f3-af60-20c1c688f5f9@intel.com> (raw)
In-Reply-To: <20251124170735.3077425-1-aleksander.lobakin@intel.com>
Tested-by: Jakub Slepecki <jakub.slepecki@intel.com>
As expected, the issue reproduced with commit 53ffcce6fe91 ("ixd: add
devlink support, 2025-11-17"). Applying this patch on top of this commit
allows VFs to receive packets. Network configuration used:
ip netns add $pf_netns
ip l set $pf netns $pf_netns
ip netns exec $pf_netns ip l set lo up
ip netns exec $pf_netns ip l set $pf address $pf_mac up
ip netns exec $pf_netns ip a add 10.0.0.1/24 dev $pf
ip netns add $vf0_netns
ip l set $vf0 netns $vf0_netns
ip netns exec $vf0_netns ip l set lo up
ip netns exec $vf0_netns ip l set $vf0 up
ip netns exec $vf0_netns ip a add 10.0.0.2/24 dev $vf0
ip netns add $vf1_netns
ip l set $vf1 netns $vf1_netns
ip netns exec $vf1_netns ip l set lo up
ip netns exec $vf1_netns ip l set $vf1 up
ip netns exec $vf1_netns ip a add 10.0.0.3/24 dev $vf1
Assume all variables are known and network namespaces are distinct.
External host was able to successfully ping each 10.0.0.[123].
next prev parent reply other threads:[~2025-11-25 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 17:07 [Intel-wired-lan] [PATCH net-next] ice: fix broken Rx on VFs Alexander Lobakin
2025-11-24 17:17 ` Alexander Lobakin
2025-11-25 6:32 ` Loktionov, Aleksandr
2025-11-25 10:59 ` Jakub Slepecki [this message]
2025-11-26 4:00 ` patchwork-bot+netdevbpf
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=159bb793-508c-42f3-af60-20c1c688f5f9@intel.com \
--to=jakub.slepecki@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nxne.cnse.osdt.itp.upstreaming@intel.com \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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