From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932454AbcHBTXx (ORCPT ); Tue, 2 Aug 2016 15:23:53 -0400 Received: from mx2.suse.de ([195.135.220.15]:41297 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932292AbcHBTXp (ORCPT ); Tue, 2 Aug 2016 15:23:45 -0400 Date: Tue, 2 Aug 2016 19:02:31 +0200 From: Michal Kubecek To: Thomas Voegtle Cc: "Levin, Alexander" , LKML , stable , Josh Hunt Subject: Re: Linux 4.1.28 Message-ID: <20160802170231.GA32623@unicorn.suse.cz> References: <5786F7BC.9090406@oracle.com> <5788CEF1.8010900@oracle.com> <20160720082943.GD17120@unicorn.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 02, 2016 at 06:14:22PM +0200, Thomas Voegtle wrote: > On Wed, 20 Jul 2016, Michal Kubecek wrote: > > >On Fri, Jul 15, 2016 at 03:04:48PM +0200, Thomas Voegtle wrote: > >>And that one? > >>Happens while trying to start a firewall script with iptables-restore. > >> > >>[ 180.071999] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > >>[iptables-restor:2338] > >... > >>[ 180.072000] Call Trace: > >>[ 180.072000] [] ? __kmalloc_node+0x26/0x2d > >>[ 180.072000] [] ? cpumask_next+0x1b/0x1d > >>[ 180.072000] [] ? xt_alloc_table_info+0xc2/0xdf > >>[ 180.072000] [] do_ipt_set_ctl+0xfd/0x193 [ip_tables] > >>[ 180.072000] [] nf_sockopt+0x64/0x7e > >>[ 180.072000] [] nf_setsockopt+0x1c/0x20 > >>[ 180.072000] [] ip_setsockopt+0x6e/0x8e > >>[ 180.072000] [] raw_setsockopt+0x11/0x4c > >>[ 180.072000] [] sock_common_setsockopt+0xf/0x11 > >>[ 180.072000] [] SyS_setsockopt+0x85/0xa5 > >>[ 180.072000] [] system_call_fastpath+0x12/0x71 > > > >This should be the problem addressed by > > > > http://article.gmane.org/gmane.linux.network/422215 > > I re-checked your patch today on top of a 4.1.29 and I'm very sorry > to say it actually does fix the problem despite what I wrote a few > days ago. > > I don't know why I saw the problem while I was sure I had that patch > applied. Maybe I mixed up the builds. Should have double checked it. > > So, if that patch would appear in the next 4.1.y, that would be great. > > talking about that patch: > https://patchwork.ozlabs.org/patch/650120/ > (as gmame is down atm) I used the old address of Sasha Levin so that he didn't get the e-mail with the patch. I'll bounce it to his new address. Michal Kubecek