From: Jakub Kicinski <kuba@kernel.org>
To: Tom Herbert <tom@herbertland.com>
Cc: davem@davemloft.net, edumazet@google.com, netdev@vger.kernel.org,
felipe@sipanda.io
Subject: Re: [PATCH 00/12] flow_dissector: Dissect UDP encapsulation protocols
Date: Thu, 1 Aug 2024 09:16:33 -0700 [thread overview]
Message-ID: <20240801091633.55b2ae5f@kernel.org> (raw)
In-Reply-To: <20240731172332.683815-1-tom@herbertland.com>
On Wed, 31 Jul 2024 10:23:20 -0700 Tom Herbert wrote:
> Add support in flow_dissector for dissecting into UDP
> encapsulations like VXLAN. __skb_flow_dissect_udp is called for
> IPPROTO_UDP. The flag FLOW_DISSECTOR_F_PARSE_UDP_ENCAPS enables parsing
> of UDP encapsulations. If the flag is set when parsing a UDP packet then
> a socket lookup is performed. The offset of the base network header,
> either an IPv4 or IPv6 header, is tracked and passed to
> __skb_flow_dissect_udp so that it can perform the socket lookup.
> If a socket is found and it's for a UDP encapsulation (encap_type is
> set in the UDP socket) then a switch is performed on the encap_type
> value (cases are UDP_ENCAP_* values)
Appears to break build for allmodconfig
--
pw-bot: cr
prev parent reply other threads:[~2024-08-01 16:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 17:23 [PATCH 00/12] flow_dissector: Dissect UDP encapsulation protocols Tom Herbert
2024-07-31 17:23 ` [PATCH 01/12] skbuff: Unconstantify struct net argument in flowdis functions Tom Herbert
2024-08-01 13:13 ` Willem de Bruijn
2024-08-02 13:33 ` Eric Dumazet
2024-08-15 18:50 ` Tom Herbert
2024-08-15 19:42 ` Tom Herbert
2024-07-31 17:23 ` [PATCH 02/12] flow_dissector: Parse ETH_P_TEB Tom Herbert
2024-08-01 13:12 ` Willem de Bruijn
2024-07-31 17:23 ` [PATCH 03/12] flow_dissector: Move ETH_P_TEB out of GRE Tom Herbert
2024-08-01 13:13 ` Willem de Bruijn
2024-07-31 17:23 ` [PATCH 04/12] udp_encaps: Add new UDP_ENCAP constants Tom Herbert
2024-08-01 13:22 ` Willem de Bruijn
2024-08-15 18:52 ` Tom Herbert
2024-07-31 17:23 ` [PATCH 05/12] udp_encaps: Set proper UDP_ENCAP types in tunnel setup Tom Herbert
2024-08-01 13:33 ` Willem de Bruijn
2024-07-31 17:23 ` [PATCH 06/12] flow_dissector: UDP encap infrastructure Tom Herbert
2024-08-01 13:58 ` Willem de Bruijn
2024-08-02 12:29 ` kernel test robot
2024-08-02 13:00 ` kernel test robot
2024-07-31 17:23 ` [PATCH 07/12] flow_dissector: Parse vxlan in UDP Tom Herbert
2024-08-01 18:22 ` Simon Horman
2024-08-03 3:26 ` kernel test robot
2024-07-31 17:23 ` [PATCH 08/12] flow_dissector: Parse foo-over-udp (FOU) Tom Herbert
2024-08-01 14:03 ` Willem de Bruijn
2024-07-31 17:23 ` [PATCH 09/12] flow_dissector: Parse ESP, L2TP, and SCTP in UDP Tom Herbert
2024-07-31 17:23 ` [PATCH 10/12] flow_dissector: Parse Geneve " Tom Herbert
2024-08-03 19:13 ` Willem de Bruijn
2024-08-03 19:19 ` Willem de Bruijn
2024-08-15 20:03 ` Tom Herbert
2024-07-31 17:23 ` [PATCH 11/12] flow_dissector: Parse GUE " Tom Herbert
2024-07-31 17:23 ` [PATCH 12/12] flow_dissector: Parse gtp " Tom Herbert
2024-08-03 19:30 ` Willem de Bruijn
2024-08-01 13:20 ` [PATCH 00/12] flow_dissector: Dissect UDP encapsulation protocols Willem de Bruijn
2024-08-14 20:28 ` Tom Herbert
2024-08-14 20:37 ` Tom Herbert
2024-08-01 16:16 ` Jakub Kicinski [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=20240801091633.55b2ae5f@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=felipe@sipanda.io \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.