Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757783AbbGQKKO (ORCPT ); Fri, 17 Jul 2015 06:10:14 -0400 Received: from Chamillionaire.breakpoint.cc ([80.244.247.6]:58298 "EHLO Chamillionaire.breakpoint.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757279AbbGQKKM (ORCPT ); Fri, 17 Jul 2015 06:10:12 -0400 Date: Fri, 17 Jul 2015 12:10:09 +0200 From: Florian Westphal To: Toralf =?iso-8859-15?Q?F=F6rster?= Cc: netfilter-devel@vger.kernel.org, Linux Kernel , Pablo Neira Ayuso , kaber@trash.net, Marcelo Leitner Subject: Re: nf_conntrack: falling back to vmalloc. Message-ID: <20150717101009.GN25674@breakpoint.cc> References: <55A8C428.1000005@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <55A8C428.1000005@gmx.de> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1932 Lines: 41 Toralf F?rster wrote: > I do run a server with a 64 bit hardened Gentoo Linux (kernel currently 4.0.8). > Around 12th of July it started to spew those messages into kern.log : > > /var/log/kern.log:Jul 12 15:26:07 tor-relay kernel: [538360.650490] nf_conntrack: falling back to vmalloc. > /var/log/kern.log:Jul 12 15:26:07 tor-relay kernel: [538360.650615] nf_conntrack: falling back to vmalloc. > /var/log/kern.log:Jul 12 15:26:08 tor-relay kernel: [538361.673649] nf_conntrack: falling back to vmalloc. > /var/log/kern.log:Jul 12 15:26:08 tor-relay kernel: [538361.673786] nf_conntrack: falling back to vmalloc. > > I read https://bugzilla.openvz.org/show_bug.cgi?id=3092 but a reboot did not help. > I got 1-2 thousends of those lines per day. Most likely result of 88eab472ec21f01d3e36ff ("netfilter: conntrack: adjust nf_conntrack_buckets default value". Do you run containers? This message can only be printed when a new network namespace is created (or something is rmmod/modprobing nf_conntrack module all the time). I wonder if this is caused by some program creating netns for sandboxing? Pablo, Patrick -- any idea on how to stop conntrack from becoming active in a newly created netns automatically without breaking anything? With upcoming per netns hooks, we might be able to delay registering conntrack, defrag etc. until after a -m conntrack rule has been added. Dou you think that could work? For nft we could create an expression to configure conntrack explicitly (inverse NOTRACK). [ obviously we can also add that for xtables but that would break setups if we suddently move to "you must ask for conntrack via ruleset" model. ] -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/