From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Use ping_command() for IPv6 pings in lwt_ip_encap
Date: Fri, 14 Aug 2026 16:30:10 +0000 [thread overview]
Message-ID: <178672501014.3867910.10216668768556024884.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813213558.3103179-1-andrii@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 13 Aug 2026 14:35:58 -0700 you wrote:
> lwt_ip_encap hardcodes the ping6 binary for its IPv6 pings. iputils
> merged ping6 into ping long ago and distros have started dropping the
> compat symlink -- Arch's iputils 20250605 ships only arping, clockdiff,
> ping and tracepath. There, every lwt_ip_encap subtest fails:
>
> check_ping_ok:FAIL:ip netns exec ns-lwt-ip-encap-1-0101330 ping6 -c 1 \
> -W1 -I veth1 fb04::1 > /dev/null unexpected error: 256 (errno 2)
> #217/1 lwt_ip_encap_ipv4/egress:FAIL
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Use ping_command() for IPv6 pings in lwt_ip_encap
https://git.kernel.org/bpf/bpf-next/c/073574da7a8e
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-08-14 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 21:35 [PATCH bpf-next] selftests/bpf: Use ping_command() for IPv6 pings in lwt_ip_encap Andrii Nakryiko
2026-08-13 21:38 ` Song Liu
2026-08-13 22:41 ` bot+bpf-ci
2026-08-14 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=178672501014.3867910.10216668768556024884.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@meta.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).