From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, daniel@iogearbox.net,
yihung.wei@gmail.com, davem@davemloft.net, bpf@vger.kernel.org,
u9012063@gmail.com
Subject: Re: [PATCH net] selftests/bpf: set gopt opt_class to 0 if get tunnel opt failed
Date: Wed, 10 Mar 2021 01:37:48 +0000 [thread overview]
Message-ID: <161534026864.31790.14467574294253275820.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210309032214.2112438-1-liuhangbin@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Tue, 9 Mar 2021 11:22:14 +0800 you wrote:
> When fixing the bpf test_tunnel.sh genve failure. I only fixed
> the IPv4 part but forgot the IPv6 issue. Similar with the IPv4
> fixes 557c223b643a ("selftests/bpf: No need to drop the packet when
> there is no geneve opt"), when there is no tunnel option and
> bpf_skb_get_tunnel_opt() returns error, there is no need to drop the
> packets and break all geneve rx traffic. Just set opt_class to 0 and
> keep returning TC_ACT_OK at the end.
>
> [...]
Here is the summary with links:
- [net] selftests/bpf: set gopt opt_class to 0 if get tunnel opt failed
https://git.kernel.org/netdev/net-next/c/557c223b643a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-03-10 1:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 3:22 [PATCH net] selftests/bpf: set gopt opt_class to 0 if get tunnel opt failed Hangbin Liu
2021-03-09 18:53 ` William Tu
2021-03-10 1:37 ` patchwork-bot+netdevbpf [this message]
2021-03-10 7:09 ` Hangbin Liu
2021-03-12 1:56 ` Hangbin Liu
2021-03-12 15:15 ` Daniel Borkmann
2021-03-15 6:57 ` Hangbin Liu
2021-03-15 16:32 ` Daniel Borkmann
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=161534026864.31790.14467574294253275820.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=u9012063@gmail.com \
--cc=yihung.wei@gmail.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).