From: Thomas Voegtle <tv@lio96.de>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: Sasha Levin <sasha.levin@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>, Josh Hunt <joshhunt00@gmail.com>
Subject: Re: Linux 4.1.28
Date: Tue, 2 Aug 2016 18:14:22 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.11.1608021720460.30752@er-systems.de> (raw)
In-Reply-To: <20160720082943.GD17120@unicorn.suse.cz>
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] [<ffffffff8111a923>] ? __kmalloc_node+0x26/0x2d
>> [ 180.072000] [<ffffffff81667495>] ? cpumask_next+0x1b/0x1d
>> [ 180.072000] [<ffffffff81668ec3>] ? xt_alloc_table_info+0xc2/0xdf
>> [ 180.072000] [<ffffffffc05be6c3>] do_ipt_set_ctl+0xfd/0x193 [ip_tables]
>> [ 180.072000] [<ffffffff81665181>] nf_sockopt+0x64/0x7e
>> [ 180.072000] [<ffffffff816651cc>] nf_setsockopt+0x1c/0x20
>> [ 180.072000] [<ffffffff81674dd1>] ip_setsockopt+0x6e/0x8e
>> [ 180.072000] [<ffffffff8168fe47>] raw_setsockopt+0x11/0x4c
>> [ 180.072000] [<ffffffff816296ab>] sock_common_setsockopt+0xf/0x11
>> [ 180.072000] [<ffffffff81628ab2>] SyS_setsockopt+0x85/0xa5
>> [ 180.072000] [<ffffffff816e7dee>] 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
next prev parent reply other threads:[~2016-08-02 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 2:23 Linux 4.1.28 Sasha Levin
2016-07-14 17:58 ` Takashi Iwai
2016-07-15 11:38 ` Thomas Voegtle
2016-07-15 11:54 ` Sasha Levin
2016-07-15 13:04 ` Thomas Voegtle
2016-07-20 6:45 ` Arkadiusz Miskiewicz
2016-07-20 7:03 ` Arkadiusz Miskiewicz
2016-07-20 8:29 ` Michal Kubecek
2016-07-20 12:13 ` Thomas Voegtle
2016-08-02 16:14 ` Thomas Voegtle [this message]
2016-08-02 17:02 ` Michal Kubecek
2016-07-29 17:24 ` Josh Hunt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LSU.2.11.1608021720460.30752@er-systems.de \
--to=tv@lio96.de \
--cc=joshhunt00@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).