patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Ivan Malov <ivan.malov@arknetworks.am>, stable@dpdk.org
Cc: Andy Moreton <amoreton@xilinx.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [PATCH 21.11] net/sfc: fix resetting mark in tunnel offload switch rules
Date: Mon, 20 Mar 2023 16:14:31 +0000	[thread overview]
Message-ID: <a021632d-5657-c23d-8a88-7fa64809fd28@redhat.com> (raw)
In-Reply-To: <20230315164453.8016-1-ivan.malov@arknetworks.am>

On 15/03/2023 16:44, Ivan Malov wrote:
> [ upstream commit dfa00c456adb6f4214b581a5e82e601e963248d2 ]
> 
> The currently used API is unfit for the purpose as it
> checks the order in which the action is being added.
> Use a dedicated API to request the reset.
> 
> Fixes: 012bf708c20f ("net/sfc: support group flows in tunnel offload")
> 
> Signed-off-by: Ivan Malov <ivan.malov@arknetworks.am>
> Reviewed-by: Andy Moreton <amoreton@xilinx.com>
> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> ---
>   drivers/net/sfc/sfc_mae.c | 8 +++-----
>   1 file changed, 3 insertions(+), 5 deletions(-)
> 

Thanks Ivan, pushed to 21.11 branch.
Kevin.

> diff --git a/drivers/net/sfc/sfc_mae.c b/drivers/net/sfc/sfc_mae.c
> index ca08bd466a..733105bc6e 100644
> --- a/drivers/net/sfc/sfc_mae.c
> +++ b/drivers/net/sfc/sfc_mae.c
> @@ -4131,12 +4131,10 @@ sfc_mae_rule_parse_actions(struct sfc_adapter *sa,
>   		break;
>   	case SFC_FT_RULE_GROUP:
>   		/*
> -		 * Packets that go to the rule's AR have FT mark set (from the
> -		 * JUMP rule OR's RECIRC_ID). Remove this mark in matching
> -		 * packets. The user may have provided their own action
> -		 * MARK above, so don't check the return value here.
> +		 * Packets that go to the rule's AR have FT mark set (from
> +		 * the JUMP rule OR's RECIRC_ID). Reset the mark to zero.
>   		 */
> -		(void)efx_mae_action_set_populate_mark(ctx.spec, 0);
> +		efx_mae_action_set_populate_mark_reset(ctx.spec);
>   
>   		ctx.ft_group_hit_counter = &spec_mae->ft->group_hit_counter;
>   		break;


      reply	other threads:[~2023-03-20 16:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 16:44 Ivan Malov
2023-03-20 16:14 ` Kevin Traynor [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=a021632d-5657-c23d-8a88-7fa64809fd28@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=amoreton@xilinx.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=ivan.malov@arknetworks.am \
    --cc=stable@dpdk.org \
    /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).