From: Greg KH <gregkh@linuxfoundation.org>
To: caojiaqiang 00593155 <caojiaqiang@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, shuah@kernel.org,
stable@vger.kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
dsahern@kernel.org
Subject: Re: [5.15.y BACKPORT] selftests: net: test_vxlan_under_vrf: fix HV connectivity test
Date: Mon, 5 Jan 2026 07:37:36 +0100 [thread overview]
Message-ID: <2026010521-removed-unclasp-f5cd@gregkh> (raw)
In-Reply-To: <20260105063805.17044-1-caojiaqiang@huawei.com>
On Mon, Jan 05, 2026 at 02:38:05PM +0800, caojiaqiang 00593155 wrote:
> From: Andrea Righi <andrea.righi@canonical.com>
>
> It looks like test_vxlan_under_vrf.sh is always failing to verify the
> connectivity test during the ping between the two simulated VMs.
>
> This is due to the fact that veth-hv in each VM should have a distinct
> MAC address.
>
> Fix by setting a unique MAC address on each simulated VM interface.
>
> Without this fix:
>
> $ sudo ./tools/testing/selftests/net/test_vxlan_under_vrf.sh
> Checking HV connectivity [ OK ]
> Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
>
> With this fix applied:
>
> $ sudo ./tools/testing/selftests/net/test_vxlan_under_vrf.sh
> Checking HV connectivity [ OK ]
> Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ]
> Check VM connectivity through VXLAN (underlay in a VRF) [FAIL]
>
> NOTE: the connectivity test with the underlay VRF is still failing; it
> seems that ARP requests are blocked at the simulated hypervisor level,
> probably due to some missing ARP forwarding rules. This requires more
> investigation (in the meantime we may consider to set that test as
> expected failure - XFAIL).
>
> Signed-off-by: Andrea Righi <andrea.righi@canonical.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> Signed-off-by: Cao Jiaqiang <caojiaqiang@huawei.com>
> ---
> tools/testing/selftests/net/test_vxlan_under_vrf.sh | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tools/testing/selftests/net/test_vxlan_under_vrf.sh b/tools/testing/selftests/net/test_vxlan_under_vrf.sh
> index 6fadc8e2f116..1fd1250ebc66 100755
> --- a/tools/testing/selftests/net/test_vxlan_under_vrf.sh
> +++ b/tools/testing/selftests/net/test_vxlan_under_vrf.sh
> @@ -101,6 +101,8 @@ setup-vm() {
> ip -netns hv-$id link set veth-tap master br0
> ip -netns hv-$id link set veth-tap up
>
> + ip link set veth-hv address 02:1d:8d:dd:0c:6$id
> +
> ip link set veth-hv netns vm-$id
> ip -netns vm-$id addr add 10.0.0.$id/24 dev veth-hv
> ip -netns vm-$id link set veth-hv up
> --
> 2.22.0
>
>
What is the git commit id of this change in Linus's tree?
thanks,
greg k-h
prev parent reply other threads:[~2026-01-05 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 6:38 [5.15.y BACKPORT] selftests: net: test_vxlan_under_vrf: fix HV connectivity test caojiaqiang 00593155
2026-01-05 6:37 ` Greg KH [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=2026010521-removed-unclasp-f5cd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=caojiaqiang@huawei.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=stable@vger.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