From: Gregory Etelson <getelson@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Raslan Darawsheh <rasland@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: RE: [PATCH] net/mlx5: fix GRE item matching
Date: Wed, 24 Nov 2021 08:16:06 +0000 [thread overview]
Message-ID: <BYAPR12MB2631D04B0C55FA55FA61CFD9A5619@BYAPR12MB2631.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211124043234.3287245-1-akozyrev@nvidia.com>
Hello Alexander,
> GRE protocol type is implicitly set in the
> matching translation in case
> an application doesn't specify any type explicitly
> in a flow rule.
> It is extracted from the inner header type, but
> this type may be absent.
> In this case, GRE item matching is broken. Check
> if we have the inner
> header type before setting it to allow matching
> on all GRE packets.
>
> Fixes: be26e81bfc1c ("net/mlx5: fix GRE protocol
> type translation")
> Cc: stable@dpdk.org
>
> Signed-off-by: Alexander Kozyrev
> <akozyrev@nvidia.com>
> ---
> drivers/net/mlx5/mlx5_flow_dv.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/mlx5/mlx5_flow_dv.c
> b/drivers/net/mlx5/mlx5_flow_dv.c
> index 9d4bd0560c..7bb092ea9f 100644
> --- a/drivers/net/mlx5/mlx5_flow_dv.c
> +++ b/drivers/net/mlx5/mlx5_flow_dv.c
> @@ -8823,8 +8823,9 @@
> flow_dv_translate_item_gre(void *matcher, void
> *key,
> protocol_v = rte_be_to_cpu_16(gre_v-
> >protocol);
> if (!protocol_m) {
> /* Force next protocol to prevent
> matchers duplication */
> - protocol_m = 0xFFFF;
> protocol_v =
> mlx5_translate_tunnel_etypes(pattern_flags);
> + if (protocol_v)
> + protocol_m = 0xFFFF;
> }
> MLX5_SET(fte_match_set_misc, misc_m,
> gre_protocol, protocol_m);
> MLX5_SET(fte_match_set_misc, misc_v,
> gre_protocol,
> --
> 2.18.2
The main idea of the be26e81bfc1c ("net/mlx5: fix GRE protocol type translation") patch
was to *always* force GRE protocol mask. Otherwise we get back to the original issue that patch has solved.
Regards,
Gregory
next prev parent reply other threads:[~2021-11-24 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 4:32 Alexander Kozyrev
2021-11-24 8:16 ` Gregory Etelson [this message]
2021-11-24 8:48 ` Gregory Etelson
2021-11-24 10:14 ` Slava Ovsiienko
2021-11-24 13:05 ` 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=BYAPR12MB2631D04B0C55FA55FA61CFD9A5619@BYAPR12MB2631.namprd12.prod.outlook.com \
--to=getelson@nvidia.com \
--cc=akozyrev@nvidia.com \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--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).