From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: "Nicolau, Radu" <radu.nicolau@intel.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>,
"Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Buckley, Daniel M" <daniel.m.buckley@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH 1/3] ipsec: fix NAT-T ports and length
Date: Tue, 14 Jun 2022 15:49:54 +0000 [thread overview]
Message-ID: <MW5PR11MB5809ADCA26CBB1A680FB6D14B8AA9@MW5PR11MB5809.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220525135912.181765-1-radu.nicolau@intel.com>
> -----Original Message-----
> From: Radu Nicolau <radu.nicolau@intel.com>
> Sent: Wednesday, May 25, 2022 2:59 PM
> To: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>; Iremonger,
> Bernard <bernard.iremonger@intel.com>; Medvedkin, Vladimir
> <vladimir.medvedkin@intel.com>
> Cc: dev@dpdk.org; Buckley, Daniel M <daniel.m.buckley@intel.com>; Zhang, Qi
> Z <qi.z.zhang@intel.com>; Nicolau, Radu <radu.nicolau@intel.com>;
> stable@dpdk.org
> Subject: [PATCH 1/3] ipsec: fix NAT-T ports and length
>
> Fix the UDP header fields, wrong byte order used for src and dst port
> and wrong offset used when updating UDP datagram length.
>
> Fixes: 01eef5907fc3 ("ipsec: support NAT-T")
> Cc: stable@dpdk.org
>
> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
> ---
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2022-06-14 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 13:59 Radu Nicolau
2022-05-25 13:59 ` [PATCH 2/3] examples/ipsec-secgw: fix NAT-T header fields Radu Nicolau
2022-06-14 15:49 ` Zhang, Roy Fan
2022-05-25 13:59 ` [PATCH 3/3] net/iavf: fix NAT-T payload length Radu Nicolau
2022-06-14 15:50 ` Zhang, Roy Fan
2022-06-14 15:49 ` Zhang, Roy Fan [this message]
2022-06-15 15:07 ` [EXT] [PATCH 1/3] ipsec: fix NAT-T ports and length Akhil Goyal
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=MW5PR11MB5809ADCA26CBB1A680FB6D14B8AA9@MW5PR11MB5809.namprd11.prod.outlook.com \
--to=roy.fan.zhang@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=daniel.m.buckley@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=qi.z.zhang@intel.com \
--cc=radu.nicolau@intel.com \
--cc=stable@dpdk.org \
--cc=vladimir.medvedkin@intel.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).