From: sdf@google.com
To: Andrea Mayer <andrea.mayer@uniroma2.it>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
David Lebrun <david.lebrun@uclouvain.be>,
Mathieu Xhonneux <m.xhonneux@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org,
Stefano Salsano <stefano.salsano@uniroma2.it>,
Paolo Lungaroni <paolo.lungaroni@uniroma2.it>,
Ahmed Abdelsalam <ahabdels.dev@gmail.com>,
Anton Makarov <anton.makarov11235@gmail.com>
Subject: Re: [net 0/3] seg6: fix skb checksum for SRH encapsulation/insertion
Date: Tue, 12 Jul 2022 15:14:50 -0700 [thread overview]
Message-ID: <Ys3yWlQT/vEpVH+i@google.com> (raw)
In-Reply-To: <20220712175837.16267-1-andrea.mayer@uniroma2.it>
On 07/12, Andrea Mayer wrote:
> The Linux kernel supports Segment Routing Header (SRH)
> encapsulation/insertion operations by providing the capability to: i)
> encapsulate a packet in an outer IPv6 header with a specified SRH; ii)
> insert a specified SRH directly after the IPv6 header of the packet.
> Note that the insertion operation is also referred to as 'injection'.
> The two operations are respectively supported by seg6_do_srh_encap() and
> seg6_do_srh_inline(), which operate on the skb associated to the packet as
> needed (e.g. adding the necessary headers and initializing them, while
> taking care to recalculate the skb checksum).
> seg6_do_srh_encap() and seg6_do_srh_inline() do not initialize the payload
> length of the IPv6 header, which is carried out by the caller functions.
> However, this approach causes the corruption of the skb checksum which
> needs to be updated only after initialization of headers is completed
> (thanks to Paolo Abeni for detecting this issue).
> The patchset fixes the skb checksum corruption by moving the IPv6 header
> payload length initialization from the callers of seg6_do_srh_encap() and
> seg6_do_srh_inline() directly into these functions.
> This patchset is organized as follows:
> - patch 1/3, seg6: fix skb checksum evaluation in SRH
> encapsulation/insertion;
> (* SRH encapsulation/insertion available since v4.10)
> - patch 2/3, seg6: fix skb checksum in SRv6 End.B6 and End.B6.Encaps
> behaviors;
> (* SRv6 End.B6 and End.B6.Encaps behaviors available since v4.14)
> - patch 3/3, seg6: bpf: fix skb checksum in bpf_push_seg6_encap();
> (* bpf IPv6 Segment Routing helpers available since v4.18)
BPF changes make sense. I've tested them by applying the whole series and
running test_lwt_seg6local.sh.
Reviewed-by: Stanislav Fomichev <sdf@google.com>
Tested-by: Stanislav Fomichev <sdf@google.com>
> Thank you all,
> Andrea
> Andrea Mayer (3):
> seg6: fix skb checksum evaluation in SRH encapsulation/insertion
> seg6: fix skb checksum in SRv6 End.B6 and End.B6.Encaps behaviors
> seg6: bpf: fix skb checksum in bpf_push_seg6_encap()
> net/core/filter.c | 1 -
> net/ipv6/seg6_iptunnel.c | 5 ++++-
> net/ipv6/seg6_local.c | 2 --
> 3 files changed, 4 insertions(+), 4 deletions(-)
> --
> 2.20.1
next prev parent reply other threads:[~2022-07-12 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 17:58 [net 0/3] seg6: fix skb checksum for SRH encapsulation/insertion Andrea Mayer
2022-07-12 17:58 ` [net 1/3] seg6: fix skb checksum evaluation in " Andrea Mayer
2022-07-12 17:58 ` [net 2/3] seg6: fix skb checksum in SRv6 End.B6 and End.B6.Encaps behaviors Andrea Mayer
2022-07-12 17:58 ` [net 3/3] seg6: bpf: fix skb checksum in bpf_push_seg6_encap() Andrea Mayer
2022-07-12 22:14 ` sdf [this message]
2022-07-14 8:30 ` [net 0/3] seg6: fix skb checksum for SRH encapsulation/insertion patchwork-bot+netdevbpf
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=Ys3yWlQT/vEpVH+i@google.com \
--to=sdf@google.com \
--cc=ahabdels.dev@gmail.com \
--cc=andrea.mayer@uniroma2.it \
--cc=andrii@kernel.org \
--cc=anton.makarov11235@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=david.lebrun@uclouvain.be \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.xhonneux@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paolo.lungaroni@uniroma2.it \
--cc=songliubraving@fb.com \
--cc=stefano.salsano@uniroma2.it \
--cc=yhs@fb.com \
--cc=yoshfuji@linux-ipv6.org \
/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