[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151025162955.GA8375@kroah.com>
Date: Mon, 26 Oct 2015 01:29:55 +0900
From: Greg KH <gregkh@...uxfoundation.org>
To: Gerhard Wiesinger <lists@...singer.com>
Cc: Willy Tarreau <w@....eu>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
netfilter-devel@...r.kernel.org, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
torvalds@...ux-foundation.org, stable@...r.kernel.org, lwn@....net,
Jiri Slaby <jslaby@...e.cz>
Subject: Re: Linux 4.2.4
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@...r.kernel.org, there's
nothing that I can do on my own about this, sorry.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists