All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Florian Westphal <fw@strlen.de>,
	netfilter-devel@vger.kernel.org,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	kaber@trash.net, Marcelo Leitner <mleitner@redhat.com>
Subject: Re: nf_conntrack: falling back to vmalloc.
Date: Fri, 17 Jul 2015 17:02:08 +0200	[thread overview]
Message-ID: <20150717150208.GO25674@breakpoint.cc> (raw)
In-Reply-To: <55A9125E.2080807@gmx.de>

Toralf Förster <toralf.foerster@gmx.de> wrote:
> On 07/17/2015 12:10 PM, Florian Westphal wrote:
> > Do you run containers?
> 
> No, I just run 4 Gentoo chroot images in parallel - but I do that since autumn last year.
> 
> Unfortunately I cannot see any correlation to an os/sw upgrade or a config change which could cause these messages nowadays to be appear.
> Therefore I do wonder if some network related "traffic" causes this, b/c that box acts as a Tor exit relay too.

No, I see no way how this would happen in response to network traffic.

A conntrack hash table is only allocated on network namespace creation, or when
a resize happens (someone changing /sys/module/nf_conntrack/parameters/hashsize).
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Florian Westphal <fw@strlen.de>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Florian Westphal <fw@strlen.de>,
	netfilter-devel@vger.kernel.org,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	kaber@trash.net, Marcelo Leitner <mleitner@redhat.com>
Subject: Re: nf_conntrack: falling back to vmalloc.
Date: Fri, 17 Jul 2015 17:02:08 +0200	[thread overview]
Message-ID: <20150717150208.GO25674@breakpoint.cc> (raw)
In-Reply-To: <55A9125E.2080807@gmx.de>

Toralf Förster <toralf.foerster@gmx.de> wrote:
> On 07/17/2015 12:10 PM, Florian Westphal wrote:
> > Do you run containers?
> 
> No, I just run 4 Gentoo chroot images in parallel - but I do that since autumn last year.
> 
> Unfortunately I cannot see any correlation to an os/sw upgrade or a config change which could cause these messages nowadays to be appear.
> Therefore I do wonder if some network related "traffic" causes this, b/c that box acts as a Tor exit relay too.

No, I see no way how this would happen in response to network traffic.

A conntrack hash table is only allocated on network namespace creation, or when
a resize happens (someone changing /sys/module/nf_conntrack/parameters/hashsize).

  reply	other threads:[~2015-07-17 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17  9:00 nf_conntrack: falling back to vmalloc Toralf Förster
2015-07-17 10:10 ` Florian Westphal
2015-07-17 10:10   ` Florian Westphal
2015-07-17 14:34   ` Toralf Förster
2015-07-17 15:02     ` Florian Westphal [this message]
2015-07-17 15:02       ` Florian Westphal
2015-07-23 10:45   ` Pablo Neira Ayuso

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=20150717150208.GO25674@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mleitner@redhat.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=toralf.foerster@gmx.de \
    /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.