From: David Miller <davem@davemloft.net>
To: idosch@mellanox.com
Cc: netdev@vger.kernel.org, jiri@mellanox.com, petrm@mellanox.com,
nird@mellanox.com, mlxsw@mellanox.com
Subject: Re: [PATCH net 0/4] mlxsw: Fix ACL actions error condition handling
Date: Fri, 03 Aug 2018 12:35:43 -0700 (PDT) [thread overview]
Message-ID: <20180803.123543.297036217821560729.davem@davemloft.net> (raw)
In-Reply-To: <20180803125744.16200-1-idosch@mellanox.com>
From: Ido Schimmel <idosch@mellanox.com>
Date: Fri, 3 Aug 2018 15:57:40 +0300
> Nir says:
>
> Two issues were lately noticed within mlxsw ACL actions error condition
> handling. The first patch deals with conflicting actions such as:
>
> # tc filter add dev swp49 parent ffff: \
> protocol ip pref 10 flower skip_sw dst_ip 192.168.101.1 \
> action goto chain 100 \
> action mirred egress redirect dev swp4
>
> The second action will never execute, however SW model allows this
> configuration, while the mlxsw driver cannot allow for it as it
> implements actions in sets of up to three actions per set with a single
> termination marking. Conflicting actions create a contradiction over
> this single marking and thus cannot be configured. The fix replaces a
> misplaced warning with an error code to be returned.
>
> Patches 2-4 fix a condition of duplicate destruction of resources. Some
> actions require allocation of specific resource prior to setting the
> action itself. On error condition this resource was destroyed twice,
> leading to a crash when using mirror action, and to a redundant
> destruction in other cases, since for error condition rule destruction
> also takes care of resource destruction. In order to fix this state a
> symmetry in behavior is added and resource destruction also takes care
> of removing the resource from rule's resource list.
Series applied, and queued up for -stable.
And thanks especially for the merge conflict heads up.
prev parent reply other threads:[~2018-08-03 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 12:57 [PATCH net 0/4] mlxsw: Fix ACL actions error condition handling Ido Schimmel
2018-08-03 12:57 ` [PATCH net 1/4] mlxsw: core_acl_flex_actions: Return error for conflicting actions Ido Schimmel
2018-08-03 13:03 ` Ido Schimmel
2018-08-03 12:57 ` [PATCH net 2/4] mlxsw: core_acl_flex_actions: Remove redundant resource destruction Ido Schimmel
2018-08-03 12:57 ` [PATCH net 3/4] mlxsw: core_acl_flex_actions: Remove redundant counter destruction Ido Schimmel
2018-08-03 12:57 ` [PATCH net 4/4] mlxsw: core_acl_flex_actions: Remove redundant mirror resource destruction Ido Schimmel
2018-08-03 19:35 ` David Miller [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=20180803.123543.297036217821560729.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nird@mellanox.com \
--cc=petrm@mellanox.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).