From owner-freebsd-stable@freebsd.org Mon Jul 27 15:50:04 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4C0A9AC256 for ; Mon, 27 Jul 2015 15:50:04 +0000 (UTC) (envelope-from freebsd-lists@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C0F7EBF6 for ; Mon, 27 Jul 2015 15:50:04 +0000 (UTC) (envelope-from freebsd-lists@gromit.dlib.vt.edu) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 0192B3CB for ; Mon, 27 Jul 2015 11:44:26 -0400 (EDT) From: Paul Mather Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: 10.2-RC1/STABLE VIMAGE memory leak progress? Message-Id: Date: Mon, 27 Jul 2015 11:44:26 -0400 To: freebsd-stable Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) X-Mailer: Apple Mail (2.2102) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jul 2015 15:50:05 -0000 I'm running 10-STABLE (which currently identifies itself as = 10.2-PRERELEASE) and lately I've started experimenting with using iocage = for Jail management. (I really like it so far.) In particular, I've = been trying out iocage's support for VNET networking that relies on = VIMAGE and uses bridge and epair for the network. I find that when I stop a VNET Jail using iocage that I get something = akin to the following in my console logs: =3D=3D=3D=3D=3D Jul 27 10:59:47 chumby kernel: vnet0:1: link state changed to DOWN Jul 27 10:59:47 chumby kernel: vnet0: link state changed to DOWN Jul 27 10:59:47 chumby kernel: re0: link state changed to DOWN Jul 27 10:59:47 chumby kernel: bridge0: link state changed to DOWN Jul 27 10:59:47 chumby kernel: vnet1:1: link state changed to DOWN Jul 27 10:59:47 chumby kernel: vnet1: link state changed to DOWN Jul 27 10:59:47 chumby kernel: bridge1: link state changed to DOWN Jul 27 10:59:47 chumby kernel: ifa_del_loopback_route: deletion failed: = 48 Jul 27 10:59:47 chumby kernel: Freed UMA keg (udp_inpcb) was not empty = (120 items). Lost 12 pages of memory. Jul 27 10:59:47 chumby kernel: Freed UMA keg (udpcb) was not empty (1169 = items). Lost 7 pages of memory. Jul 27 10:59:47 chumby kernel: hhook_vnet_uninit: hhook_head type=3D1, = id=3D1 cleanup required Jul 27 10:59:47 chumby kernel: hhook_vnet_uninit: hhook_head type=3D1, = id=3D0 cleanup required =3D=3D=3D=3D=3D I found a PR (kern/164763) dating back to 2012-02-04 describing the = problem. The last update on that PR was on 2014-10-17, which made = reference to some unmerged fixes that would be good to merge into HEAD. Does anyone know whether this was done? One of the entries in that PR states, "Our current rule of thumb is 'if = you need to shutdown one vimage jail then you need to reboot the host.'" = It then goes on to observe, "Of course this is far from optimal." Is it safe to say, then, that dynamic VNET Jails are not recommended = still under FreeBSD? Judging by that PR, this is not likely to be fixed for 10.2-RELEASE? Cheers, Paul.