From: Gerhard Wiesinger <lists@wiesinger.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Willy Tarreau <w@1wt.eu>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
netfilter-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>
Subject: Re: Linux 4.2.4
Date: Sun, 8 Nov 2015 14:51:01 +0100 [thread overview]
Message-ID: <563F5345.7060001@wiesinger.com> (raw)
In-Reply-To: <20151025162955.GA8375@kroah.com>
On 25.10.2015 17:29, Greg KH wrote:
> On Sun, Oct 25, 2015 at 11:48:54AM +0100, Gerhard Wiesinger wrote:
>> On 25.10.2015 10:46, Willy Tarreau wrote:
>>> ipset *triggered* the problem. The whole stack dump would tell more.
>> OK, find the stack traces in the bug report:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1272645
>>
>> Kernel 4.1.10 triggered also a kernel dump when playing with ipset commands
>> and IPv6, details in the bug report ....
>>
>>>> Kernel 4.2 seems to me not well tested in the netfilter parts at all
>>>> (Bug with already known bugfix
>>>> https://lists.debian.org/debian-kernel/2015/10/msg00034.html was
>>>> triggered on 2 of 3 of my machines, the new bug on 1 of 1 tested machine).
>>> There's a reason why Greg maintains stable and LTS kernels :-)
>> Stable kernels don't crash but definiton. :-)
>>
>> At least triggered 2 kernel panics in 5min, even with 4.1.10 and ipset
>> commands ...
> Does this happen also with Linus's tree? I suggest you ask the
> networking developers about this on netdev@vger.kernel.org, there's
> nothing that I can do on my own about this, sorry.
Patch is now available, see:
[PATCH 0/3] ipset patches for nf
https://marc.info/?l=netfilter-devel&m=144690007708041&w=2
https://marc.info/?l=netfilter-devel&m=144690007808042&w=2
https://marc.info/?l=netfilter-devel&m=144690008608043&w=2
https://marc.info/?l=netfilter-devel&m=144690007708039&w=2
[ANNOUNCE] ipset 6.27 released
https://marc.info/?l=netfilter-devel&m=144690048308099&w=2
Requires also new userland ipset version.
Please integrate it upstream.
Thanx to Jozsef Kadlecsik for fixing it.
Ciao,
Gerhard
next prev parent reply other threads:[~2015-11-08 13:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151023003306.GA25388@kroah.com>
[not found] ` <562C83FD.6010402@wiesinger.com>
[not found] ` <20151025082547.GA22300@kroah.com>
[not found] ` <20151025090308.GA17656@1wt.eu>
[not found] ` <562CA13C.90500@wiesinger.com>
[not found] ` <20151025094634.GA6832@1wt.eu>
2015-10-25 10:48 ` Linux 4.2.4 Gerhard Wiesinger
2015-10-25 16:29 ` Greg KH
2015-10-25 17:14 ` Gerhard Wiesinger
2015-11-08 13:51 ` Gerhard Wiesinger [this message]
2015-11-08 17:20 ` Greg KH
2015-11-09 12:35 ` Gerhard Wiesinger
2015-11-09 12:41 ` Pablo Neira Ayuso
2015-10-25 19:46 ` Jozsef Kadlecsik
2015-10-25 20:08 ` Gerhard Wiesinger
2015-10-25 21:26 ` Gerhard Wiesinger
2015-10-25 21:53 ` Jozsef Kadlecsik
2015-10-26 7:27 ` Gerhard Wiesinger
2015-10-26 8:58 ` Jozsef Kadlecsik
2015-10-26 9:11 ` Gerhard Wiesinger
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=563F5345.7060001@wiesinger.com \
--to=lists@wiesinger.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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).