From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935241AbcHBQTV (ORCPT ); Tue, 2 Aug 2016 12:19:21 -0400 Received: from er-systems.de ([148.251.68.21]:45259 "EHLO er-systems.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935245AbcHBQOt (ORCPT ); Tue, 2 Aug 2016 12:14:49 -0400 Date: Tue, 2 Aug 2016 18:14:22 +0200 (CEST) From: Thomas Voegtle X-X-Sender: thomas@er-systems.de To: Michal Kubecek cc: Sasha Levin , LKML , stable , Josh Hunt Subject: Re: Linux 4.1.28 In-Reply-To: <20160720082943.GD17120@unicorn.suse.cz> Message-ID: References: <5786F7BC.9090406@oracle.com> <5788CEF1.8010900@oracle.com> <20160720082943.GD17120@unicorn.suse.cz> User-Agent: Alpine 2.11 (LSU 23 2013-08-11) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Virus-Checker-Version: clamassassin 1.2.4 with clamdscan / ClamAV 0.99.2/22014/Tue Aug 2 13:11:12 2016 signatures 57. Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > > Michal Kubecek Hi, 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) thanks, Thomas