From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamal Hadi Salim Subject: Re: [PATCH net-next v2] net: sched: don't disable bh when accessing action idr Date: Tue, 22 May 2018 08:50:06 -0400 Message-ID: <1719721d-35ed-7baa-6dec-c3f7f6fc79ff@mojatatu.com> References: <20180519.230258.1374885458106197707.davem@davemloft.net> <1526932984-11544-1-git-send-email-vladbu@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, xiyou.wangcong@gmail.com, jiri@resnulli.us, linux-kernel@vger.kernel.org To: Vlad Buslov , davem@davemloft.net Return-path: In-Reply-To: <1526932984-11544-1-git-send-email-vladbu@mellanox.com> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 21/05/18 04:03 PM, Vlad Buslov wrote: > Initial net_device implementation used ingress_lock spinlock to synchronize > ingress path of device. This lock was used in both process and bh context. > In some code paths action map lock was obtained while holding ingress_lock. > Commit e1e992e52faa ("[NET_SCHED] protect action config/dump from irqs") > modified actions to always disable bh, while using action map lock, in > order to prevent deadlock on ingress_lock in softirq. This lock was removed > from net_device, so disabling bh, while accessing action map, is no longer > necessary. > > Replace all action idr spinlock usage with regular calls that do not > disable bh. > > Signed-off-by: Vlad Buslov Acked-by: Jamal Hadi Salim cheers, jamal