From: Raslan Darawsheh <rasland@nvidia.com>
To: Viacheslav Ovsiienko <viacheslavo@nvidia.com>, dev@dpdk.org
Cc: matan@nvidia.com, suanmingm@nvidia.com, dsosnowski@nvidia.com,
stable@dpdk.org
Subject: Re: [PATCH] net/mlx5/hws: fix ESP header match in strict mode
Date: Mon, 18 Aug 2025 09:33:21 +0300 [thread overview]
Message-ID: <9769c8e7-3259-43c5-812e-c61fe3e3f1ca@nvidia.com> (raw)
In-Reply-To: <20250804050514.244896-1-viacheslavo@nvidia.com>
Hi,
On 04/08/2025 8:05 AM, Viacheslav Ovsiienko wrote:
> The pattern like "eth / ipv6 / esp / end" matched on any IPv6
> packet in strict mode, because there was no impicit 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: 18ca4a4ec73a ("net/mlx5: support ESP SPI match and RSS hash")
> Cc: stable@dpdk.org
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
next prev parent reply other threads:[~2025-08-18 6:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 5:05 [PATCH] net/mlx5/hws: fix ESP header match in strict mode Viacheslav Ovsiienko
2025-08-08 7:30 ` Dariusz Sosnowski
2025-08-18 6:33 ` Raslan Darawsheh [this message]
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 ` [PATCH v2 1/3] net/mlx5: fix ESP header match in strict mode Raslan Darawsheh
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=9769c8e7-3259-43c5-812e-c61fe3e3f1ca@nvidia.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@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 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.