stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gerhard Wiesinger <lists@wiesinger.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: 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 10:00:21 +0100	[thread overview]
Message-ID: <562C9A25.9080101@wiesinger.com> (raw)
In-Reply-To: <20151025082547.GA22300@kroah.com>

On 25.10.2015 09:25, Greg KH wrote:
> On Sun, Oct 25, 2015 at 08:25:49AM +0100, Gerhard Wiesinger wrote:
>> On 23.10.2015 02:33, Greg KH wrote:
>>> I'm announcing the release of the 4.2.4 kernel.
>>>
>>> All users of the 4.2 kernel series must upgrade.
>>>
>>> The updated 4.2.y git tree can be found at:
>>> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.2.y
>>> and can be browsed at the normal kernel.org git web browser:
>>> 	http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
>>>
>>> thanks,
>>>
>>> greg k-h
>>>
>> Hello Greg,
>>
>> Kernel 4.2.4 is still broken regarding iptables/ipset:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1272645
>>
>> Kernel 4.1.10 works well.
>>
>> Please fix it ASAP.
> Fix it with what patch?

Don't know, just detected it. I think this is a new issue introduced 
with 4.2.x by reworking the "new allocator api" but it is just a guess 
what I saw so far. I was not involved in development.

Can you read something from the fedora bug report?

There were already some fixes in 4.2.4 but I guess there are still 
unknown bugs introduced with 4.2.x.

The already fixed ones merged in 4.2.4:
https://lists.debian.org/debian-kernel/2015/10/msg00034.html

Thank you.

Ciao,
Gerhard


  reply	other threads:[~2015-10-25  9:00 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 [this message]
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
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=562C9A25.9080101@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=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).