From: Simon Horman <simon.horman@corigine.com>
To: "Maciej Żenczykowski" <maze@google.com>
Cc: "Maciej Żenczykowski" <zenczykowski@gmail.com>,
"Linux Network Development Mailing List" <netdev@vger.kernel.org>,
"Sabrina Dubroca" <sd@queasysnail.net>,
"Steffen Klassert" <steffen.klassert@secunet.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Benedict Wong" <benedictwong@google.com>,
"Yan Yan" <evitayan@google.com>
Subject: Re: [PATCH v2] xfrm: fix inbound ipv4/udp/esp packets to UDPv6 dualstack sockets
Date: Mon, 5 Jun 2023 15:04:25 +0200 [thread overview]
Message-ID: <ZH3dWcEqlEy5twJC@corigine.com> (raw)
In-Reply-To: <20230605110654.809655-1-maze@google.com>
On Mon, Jun 05, 2023 at 04:06:54AM -0700, Maciej Żenczykowski wrote:
> Before Linux v5.8 an AF_INET6 SOCK_DGRAM (udp/udplite) socket
> with SOL_UDP, UDP_ENCAP, UDP_ENCAP_ESPINUDP{,_NON_IKE} enabled
> would just unconditionally use xfrm4_udp_encap_rcv(), afterwards
> such a socket would use the newly added xfrm6_udp_encap_rcv()
> which only handles IPv6 packets.
>
> Cc: Sabrina Dubroca <sd@queasysnail.net>
> Cc: Steffen Klassert <steffen.klassert@secunet.com>
> Cc: Jakub Kicinski <kuba@kernel.org>
> Cc: Benedict Wong <benedictwong@google.com>
> Cc: Yan Yan <evitayan@google.com>
> Fixes: 0146dca70b87 ('xfrm: add support for UDPv6 encapsulation of ESP')
Nit, which can possibly fixed without reposting. This should probably be:
Fixes: 0146dca70b87 ("xfrm: add support for UDPv6 encapsulation of ESP")
next prev parent reply other threads:[~2023-06-05 13:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 8:32 [PATCH] xfrm: fix inbound ipv4/udp/esp packets to UDPv6 dualstack sockets Maciej Żenczykowski
2022-10-26 8:42 ` Maciej Żenczykowski
2022-10-27 1:24 ` Jakub Kicinski
2022-10-27 1:52 ` Maciej Żenczykowski
2022-10-27 1:58 ` Jakub Kicinski
2022-10-27 4:47 ` kernel test robot
2023-06-05 11:06 ` [PATCH v2] " Maciej Żenczykowski
2023-06-05 12:59 ` Simon Horman
2023-06-05 21:38 ` Maciej Żenczykowski
2023-06-06 9:30 ` Simon Horman
2023-06-07 9:41 ` Steffen Klassert
2023-06-07 15:00 ` Sabrina Dubroca
2023-06-05 13:04 ` Simon Horman [this message]
2023-06-09 7:17 ` Steffen Klassert
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=ZH3dWcEqlEy5twJC@corigine.com \
--to=simon.horman@corigine.com \
--cc=benedictwong@google.com \
--cc=evitayan@google.com \
--cc=kuba@kernel.org \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
--cc=steffen.klassert@secunet.com \
--cc=zenczykowski@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 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.