From: Ziyang Xuan <william.xuanziyang@huawei.com>
To: <ast@kernel.org>, <daniel@iogearbox.net>, <andrii@kernel.org>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <bpf@vger.kernel.org>,
<netdev@vger.kernel.org>, <martin.lau@linux.dev>,
<song@kernel.org>, <yhs@fb.com>, <john.fastabend@gmail.com>,
<kpsingh@kernel.org>, <sdf@google.com>, <haoluo@google.com>,
<jolsa@kernel.org>
Subject: [PATCH bpf-next 0/2] bpf: Add ipip6 and ip6ip decap support for bpf_skb_adjust_room()
Date: Fri, 6 Jan 2023 11:55:19 +0800 [thread overview]
Message-ID: <cover.1672976410.git.william.xuanziyang@huawei.com> (raw)
Add ipip6 and ip6ip decap support for bpf_skb_adjust_room().
Main use case is for using cls_bpf on ingress hook to decapsulate
IPv4 over IPv6 and IPv6 over IPv4 tunnel packets.
And add ipip6 and ip6ip decap testcases to verify that
bpf_skb_adjust_room() correctly decapsulate ipip6 and ip6ip
tunnel packets.
Ziyang Xuan (2):
bpf: Add ipip6 and ip6ip decap support for bpf_skb_adjust_room()
selftests/bpf: add ipip6 and ip6ip decap to test_tc_tunnel
net/core/filter.c | 34 +++++++++-
.../selftests/bpf/progs/test_tc_tunnel.c | 64 +++++++++++++++++++
tools/testing/selftests/bpf/test_tc_tunnel.sh | 15 +++--
3 files changed, 105 insertions(+), 8 deletions(-)
--
2.25.1
next reply other threads:[~2023-01-06 3:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 3:55 Ziyang Xuan [this message]
2023-01-06 3:55 ` [PATCH bpf-next 1/2] bpf: Add ipip6 and ip6ip decap support for bpf_skb_adjust_room() Ziyang Xuan
2023-01-06 19:55 ` sdf
2023-01-08 19:16 ` Willem de Bruijn
2023-01-09 9:19 ` Ziyang Xuan (William)
2023-01-09 13:32 ` Willem de Bruijn
2023-01-10 13:07 ` Ziyang Xuan (William)
2023-01-10 14:09 ` Willem de Bruijn
2023-01-11 2:37 ` Ziyang Xuan (William)
2023-01-06 3:55 ` [PATCH bpf-next 2/2] selftests/bpf: add ipip6 and ip6ip decap to test_tc_tunnel Ziyang Xuan
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=cover.1672976410.git.william.xuanziyang@huawei.com \
--to=william.xuanziyang@huawei.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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