From: patchwork-bot+netdevbpf@kernel.org
To: Qiliang Yuan <odys.yuan@gmail.com>
Cc: andrii@kernel.org, eddyz87@gmail.com, ihor.solodrai@linux.dev,
ast@kernel.org, daniel@iogearbox.net, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, shuah@kernel.org,
fankaixi.li@bytedance.com, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Create the vxlan devices of test_tunnel with their MAC
Date: Thu, 15 Oct 2026 16:30:06 +0000 [thread overview]
Message-ID: <179208180656.3995356.3658263432138680681.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261009-selftests-bpf-tunnel-vxlan-mac-v1-1-624dd769c334@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 09 Oct 2026 09:48:44 +0800 you wrote:
> The vxlan tests of test_tunnel create a tunnel device in the initial
> netns with "ip link add", and then give it the MAC address that the
> static neighbor entry at the other end points to with "ip link set".
>
> systemd-udevd assigns new devices of the initial netns a MAC address of
> its own, following its MACAddressPolicy, when it handles their uevent.
> When it gets to that after the test set the address, the replies sent
> to the configured MAC are dropped as meant for another host, and the
> ping of vxlan_tunnel fails after 10 seconds.
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Create the vxlan devices of test_tunnel with their MAC
https://git.kernel.org/bpf/bpf-next/c/33cbc5c2cadf
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-10-15 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 1:48 [PATCH bpf-next] selftests/bpf: Create the vxlan devices of test_tunnel with their MAC Qiliang Yuan
2026-10-15 16: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=179208180656.3995356.3658263432138680681.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=fankaixi.li@bytedance.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=odys.yuan@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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.