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,
jiong.wang@netronome.com
Subject: Re: [PATCH net] selftest/bpf: no need to drop the packet when there is no geneve opt
Date: Wed, 24 Feb 2021 20:40:06 +0000 [thread overview]
Message-ID: <161419920668.16624.1337615822618537205.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210224081403.1425474-1-liuhangbin@gmail.com>
Hello:
This patch was applied to bpf/bpf.git (refs/heads/master):
On Wed, 24 Feb 2021 16:14:03 +0800 you wrote:
> In bpf geneve tunnel test we set geneve option on tx side. On rx side we
> only call bpf_skb_get_tunnel_opt(). Since commit 9c2e14b48119 ("ip_tunnels:
> Set tunnel option flag when tunnel metadata is present") geneve_rx() will
> not add TUNNEL_GENEVE_OPT flag if there is no geneve option, which cause
> bpf_skb_get_tunnel_opt() return ENOENT and _geneve_get_tunnel() in
> test_tunnel_kern.c drop the packet.
>
> [...]
Here is the summary with links:
- [net] selftest/bpf: no need to drop the packet when there is no geneve opt
https://git.kernel.org/bpf/bpf/c/557c223b643a
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:[~2021-02-24 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 8:14 [PATCH net] selftest/bpf: no need to drop the packet when there is no geneve opt Hangbin Liu
2021-02-24 19:17 ` William Tu
2021-02-24 20:40 ` 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=161419920668.16624.1337615822618537205.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=jiong.wang@netronome.com \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--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).