From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net] net, sched: fix soft lockup in tc_classify Date: Thu, 22 Dec 2016 11:53:26 -0500 (EST) Message-ID: <20161222.115326.376675148706578174.davem@davemloft.net> References: <585ADFEB.3030206@iogearbox.net> <585AEF24.4070800@iogearbox.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: xiyou.wangcong@gmail.com, shahark@mellanox.com, gerlitz.or@gmail.com, roid@mellanox.com, jiri@mellanox.com, john.fastabend@gmail.com, netdev@vger.kernel.org To: daniel@iogearbox.net Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:47060 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S941270AbcLVQxa (ORCPT ); Thu, 22 Dec 2016 11:53:30 -0500 In-Reply-To: <585AEF24.4070800@iogearbox.net> Sender: netdev-owner@vger.kernel.org List-ID: From: Daniel Borkmann Date: Wed, 21 Dec 2016 22:07:48 +0100 > Ok, you mean for net. In that case I prefer the smaller sized fix to > be honest. It also covers everything from the point where we fetch > the chain via cops->tcf_chain() to the end of the function, which is > where most of the complexity resides, and only the two mentioned > commits do the relock, so as a fix I think it's fine as-is. As > mentioned, if there's need to refactor tc_ctl_tfilter() net-next > would be better, imho. Please, can you two work towards an agreement as to what fix should go in at this time? Thanks.