From: Raslan Darawsheh <rasland@nvidia.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Bill Zhou <dongzhou@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] net/mlx5: fix push VLAN action validation
Date: Thu, 10 Mar 2022 09:20:11 +0000 [thread overview]
Message-ID: <BYAPR12MB307857D95E125C6D6CDD1096CF0B9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220309093920.979934-1-dsosnowski@nvidia.com>
Hi,
> -----Original Message-----
> From: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Sent: Wednesday, March 9, 2022 11:39 AM
> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Bill Zhou <dongzhou@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>;
> stable@dpdk.org
> Subject: [PATCH] net/mlx5: fix push VLAN action validation
>
> Flow domain and direction was validated when OF_PUSH_VLAN action
> appears in flow actions. Flow was rejected whenever this action:
>
> - was used in NIC domain, in ingress direction;
> - was used in FDB domain, in ingress direction, on ConnectX-5.
>
> This validation logic rejected a valid case when the OF_PUSH_VLAN
> action was used when directing traffic to the hairpin queue,
> configured in TX implicit mode.
>
> This patch moves code responsible for OF_PUSH_VLAN validation of
> domain and direction from flow_dv_validate_push_vlan() to
> flow_dv_validate(). Domain and direction are now validated when either
> non-hairpin queue is used or hairpin queue is configured in Tx explicit
> mode.
>
> Fixes: 96f85ec489db ("net/mlx5: check VLAN push/pop support")
> Cc: dongzhou@nvidia.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-03-10 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 9:39 Dariusz Sosnowski
2022-03-10 9:20 ` 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=BYAPR12MB307857D95E125C6D6CDD1096CF0B9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=dongzhou@nvidia.com \
--cc=dsosnowski@nvidia.com \
--cc=matan@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).