From: patchwork-bot+netdevbpf@kernel.org
To: Felix Maurer <fmaurer@redhat.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
posk@google.com
Subject: Re: [PATCH bpf-next] selftests: bpf: Make test_lwt_ip_encap more stable and faster
Date: Tue, 08 Mar 2022 15:10:10 +0000 [thread overview]
Message-ID: <164675221017.28766.15263486307826146656.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <4987d549d48b4e316cd5b3936de69c8d4bc75a4f.1646305899.git.fmaurer@redhat.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 3 Mar 2022 12:15:26 +0100 you wrote:
> In test_lwt_ip_encap, the ingress IPv6 encap test failed from time to
> time. The failure occured when an IPv4 ping through the IPv6 GRE
> encapsulation did not receive a reply within the timeout. The IPv4 ping
> and the IPv6 ping in the test used different timeouts (1 sec for IPv4
> and 6 sec for IPv6), probably taking into account that IPv6 might need
> longer to successfully complete. However, when IPv4 pings (with the
> short timeout) are encapsulated into the IPv6 tunnel, the delays of IPv6
> apply.
>
> [...]
Here is the summary with links:
- [bpf-next] selftests: bpf: Make test_lwt_ip_encap more stable and faster
https://git.kernel.org/bpf/bpf-next/c/d23a8720327d
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:[~2022-03-08 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 11:15 [PATCH bpf-next] selftests: bpf: Make test_lwt_ip_encap more stable and faster Felix Maurer
2022-03-08 15:10 ` 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=164675221017.28766.15263486307826146656.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=fmaurer@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=posk@google.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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