netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gerhard Wiesinger <lists@wiesinger.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Willy Tarreau <w@1wt.eu>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	netfilter-devel@vger.kernel.org,
	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: Mon, 26 Oct 2015 10:11:11 +0100	[thread overview]
Message-ID: <562DEE2F.6030809@wiesinger.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1510260945510.17014@blackhole.kfki.hu>

On 26.10.2015 09:58, Jozsef Kadlecsik wrote:
> On Sun, 25 Oct 2015, Gerhard Wiesinger wrote:
>
>> Also any idea regarding the second isssue? Or do you think it has the
>> same root cause?
> Looking at your RedHat bugzilla report, the "nf_conntrack: table full,
> dropping packet" and "Alignment trap: not handling instruction" are two
> unrelated issues and the second one is triggered by the unaligned counter
> extension acccess in ipset, I'm investigating. I can't think of any reason
> how those issues could be related to each other.

Yes, they are unrelated.
Issue 1: nf_conntrack: table full, dropping packet => Fixed with 4.2.4
Issue 2: Alignment trap: not handling instruction => Happens when ipset 
counters are enabled

Please keep in mind it happens with IPv6 commands.

Currently 4.2.4 without ipset counters runs well.

Ciao,
Gerhard

      reply	other threads:[~2015-10-26  9:11 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
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 [this message]

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=562DEE2F.6030809@wiesinger.com \
    --to=lists@wiesinger.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=kadlec@blackhole.kfki.hu \
    --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).