From: Gerhard Wiesinger <lists@wiesinger.com>
To: Willy Tarreau <w@1wt.eu>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
netfilter-devel@vger.kernel.org
Cc: Greg KH <gregkh@linuxfoundation.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, 25 Oct 2015 11:48:54 +0100 [thread overview]
Message-ID: <562CB396.2080509@wiesinger.com> (raw)
In-Reply-To: <20151025094634.GA6832@1wt.eu>
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 ...
Ciao,
Gerhard
next prev parent reply other threads:[~2015-10-25 10:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 0:33 Linux 4.2.4 Greg KH
2015-10-23 0:33 ` Greg KH
2015-10-25 7:25 ` Gerhard Wiesinger
2015-10-25 8:25 ` Greg KH
2015-10-25 9:00 ` Gerhard Wiesinger
2015-10-25 9:03 ` Willy Tarreau
2015-10-25 9:30 ` Gerhard Wiesinger
2015-10-25 9:46 ` Willy Tarreau
2015-10-25 10:48 ` Gerhard Wiesinger [this message]
2015-10-25 16:29 ` Greg KH
2015-10-25 17:14 ` Gerhard Wiesinger
2015-11-08 13:51 ` Gerhard Wiesinger
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=562CB396.2080509@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.