From owner-freebsd-stable@FreeBSD.ORG Wed Oct 1 18:49:58 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 68F0999B; Wed, 1 Oct 2014 18:49:58 +0000 (UTC) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 161E05E8; Wed, 1 Oct 2014 18:49:58 +0000 (UTC) Received: by mail-ig0-f170.google.com with SMTP id l13so168107iga.5 for ; Wed, 01 Oct 2014 11:49:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KmERQncIJsNssSGo8nUayNJgjU7EzoJPPhNDzEk6HT0=; b=vKZz5OayA5nJeIzpBK3yphA8ojNwe+L9o7s7dGczNmzoRnO4ci+OX89E1WzX1Fm352 Hgn+Um3hOI2o1MBbkqoacFx1ZqPBr78XZwRlNZVo1y+nE7xnL1oraSCxdUE/Keky2MgQ VlDp8eo0buVzg3iRcXTeZoIjdI/WhffVJn3a+Q+KLsviYZKDt687UvDVwRWvJvdwkJPJ p1mgMGa4VvVKKA5Gnecx8hvyrgrSuTfNs+x+oFtG3BeBbH1eCnpl5F/S5X89O6TEzHuO /pIKFgSWjmVRje/Te+k2TZbiL4BK5WDFC2Uo0XNg0fSlPhQCx5sXtyqs+NZYMMjr8SNp yvVA== MIME-Version: 1.0 X-Received: by 10.50.61.144 with SMTP id p16mr22227133igr.38.1412189397397; Wed, 01 Oct 2014 11:49:57 -0700 (PDT) Received: by 10.50.87.130 with HTTP; Wed, 1 Oct 2014 11:49:57 -0700 (PDT) In-Reply-To: <20141001171646.GQ73266@glebius.int.ru> References: <542AAA3C.1080803@ipfw.ru> <542AE376.6000003@FreeBSD.org> <542AFAE3.9030705@FreeBSD.org> <20141001135124.GM73266@glebius.int.ru> <542C20D7.3070606@sentex.net> <20141001171646.GQ73266@glebius.int.ru> Date: Wed, 1 Oct 2014 11:49:57 -0700 Message-ID: Subject: Re: 10.1-BETA2 possible kernel memory leak in routing table From: Rumen Telbizov To: Gleb Smirnoff Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-stable@freebsd.org" , "Alexander V. Chernikov" , brian@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2014 18:49:58 -0000 Submitted PR with details at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194078 On Wed, Oct 1, 2014 at 10:16 AM, Gleb Smirnoff wrote: > On Wed, Oct 01, 2014 at 11:42:15AM -0400, Mike Tancsa wrote: > M> On 10/1/2014 9:51 AM, Gleb Smirnoff wrote: > M> > On Tue, Sep 30, 2014 at 04:56:00PM -0700, Rumen Telbizov wrote: > M> > R> Brian Somers and I are currently looking into the source of PF in > latest > M> > R> 10-STABLE and trying to figure out what is going on. We were able > to > M> > R> replicate this problem on a 11-CURRENT (Sep 12th) machine as well. > A simple > M> > R> PF ruleset with 1 rule and 1 table. Every few reloads of the > firewall > M> > R> and vmstat > M> > R> -m | grep routetbl shows increased memory usage. > M> > > M> > I plugged the easy leak, but there is also a hard one. Actually, the > M> > entire pf_table.c needs a good shake. Right now I am out of time for > this. > M> > M> Is that easy fix > M> > M> > http://lists.freebsd.org/pipermail/svn-src-head/2014-October/063178.html > > Yes, it seems the leak slowed down. > > M> Also, is there any work around to this ? I tried a simple set of pf > M> rules with no tables, hoping that was the cause of it, but memory grows > M> with each pf reload. > > No workaround available. Can you please file a PR for that? Once I have > time, I will work on this. > > -- > Totus tuus, Glebius. > -- Rumen Telbizov Unix Systems Administrator