From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next] net: sched: act_nat: remove dependency on
 rtnl lock
Date: Sat, 08 Sep 2018 10:18:43 -0700 (PDT)
Message-ID: <20180908.101843.1831033373502777022.davem@davemloft.net>
References: <1535958560-6967-1-git-send-email-vladbu@mellanox.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: netdev@vger.kernel.org, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
        jiri@resnulli.us
To: vladbu@mellanox.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([23.128.96.9]:34874 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1726765AbeIHWFL (ORCPT
        <rfc822;netdev@vger.kernel.org>); Sat, 8 Sep 2018 18:05:11 -0400
In-Reply-To: <1535958560-6967-1-git-send-email-vladbu@mellanox.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Vlad Buslov <vladbu@mellanox.com>
Date: Mon,  3 Sep 2018 10:09:20 +0300

> According to the new locking rule, we have to take tcf_lock for both
> ->init() and ->dump(), as RTNL will be removed.
> 
> Use tcf spinlock to protect private nat action data from concurrent
> modification during dump. (nat init already uses tcf spinlock when changing
> action state)
> 
> Signed-off-by: Vlad Buslov <vladbu@mellanox.com>

Also applied, thanks.