From: Raslan Darawsheh <rasland@nvidia.com>
To: Maayan Kashani <mkashani@nvidia.com>, dev@dpdk.org
Cc: dsosnowski@nvidia.com,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
stable@dpdk.org, Matan Azrad <matan@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Hamdan Igbaria <hamdani@nvidia.com>
Subject: Re: [PATCH v2 1/3] net/mlx5: fix ESP header match in strict mode
Date: Wed, 10 Sep 2025 10:48:10 +0300 [thread overview]
Message-ID: <3508a4fc-34c8-4cc1-8a81-79ee6829237f@nvidia.com> (raw)
In-Reply-To: <20250909062853.60592-1-mkashani@nvidia.com>
Hi,
On 09/09/2025 9:28 AM, Maayan Kashani wrote:
> From: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
>
> The pattern like "eth / ipv6 / esp / end" matched on any IPv6
> packet in strict mode, because there was no implicit match on the
> IP.proto forced.
>
> This patch adds the implicit match on IP.proto with value 50 (ESP)
> and adds implicit match on UDP.dport with value 4500 for the case
> ESP over UDP.
>
> Fixes: 81cf20a25abf ("net/mlx5/hws: support match on ESP item")
> Cc: stable@dpdk.org
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
Series applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2025-09-10 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 5:05 [PATCH] net/mlx5/hws: " Viacheslav Ovsiienko
2025-08-08 7:30 ` Dariusz Sosnowski
2025-08-18 6:33 ` Raslan Darawsheh
2025-09-08 12:12 ` Maayan Kashani
2025-09-08 12:26 ` Raslan Darawsheh
2025-09-09 6:28 ` [PATCH v2 1/3] net/mlx5: " Maayan Kashani
2025-09-09 6:28 ` [PATCH v2 2/3] net/mlx5: fix ESP item validation to match on seqnum Maayan Kashani
2025-09-09 6:28 ` [PATCH v2 3/3] net/mlx5: fix ESP header match after UDP for group 0 Maayan Kashani
2025-09-10 7:48 ` Raslan Darawsheh [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=3508a4fc-34c8-4cc1-8a81-79ee6829237f@nvidia.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=hamdani@nvidia.com \
--cc=matan@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.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).