From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net 0/4] mlxsw: Fix ACL actions error condition handling Date: Fri, 03 Aug 2018 12:35:43 -0700 (PDT) Message-ID: <20180803.123543.297036217821560729.davem@davemloft.net> References: <20180803125744.16200-1-idosch@mellanox.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, jiri@mellanox.com, petrm@mellanox.com, nird@mellanox.com, mlxsw@mellanox.com To: idosch@mellanox.com Return-path: Received: from shards.monkeyblade.net ([23.128.96.9]:38530 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728470AbeHCVd2 (ORCPT ); Fri, 3 Aug 2018 17:33:28 -0400 In-Reply-To: <20180803125744.16200-1-idosch@mellanox.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Ido Schimmel 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.