From owner-freebsd-bugs@FreeBSD.ORG  Wed Jan  9 09:40:01 2013
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id AACBDC27
 for <freebsd-bugs@smarthost.ysv.freebsd.org>;
 Wed,  9 Jan 2013 09:40:01 +0000 (UTC)
 (envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2001:1900:2254:206c::16:87])
 by mx1.freebsd.org (Postfix) with ESMTP id 83254DF
 for <freebsd-bugs@smarthost.ysv.freebsd.org>;
 Wed,  9 Jan 2013 09:40:01 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
 by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r099e1fA009767
 for <freebsd-bugs@freefall.freebsd.org>; Wed, 9 Jan 2013 09:40:01 GMT
 (envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
 by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r099e1E0009766;
 Wed, 9 Jan 2013 09:40:01 GMT (envelope-from gnats)
Date: Wed, 9 Jan 2013 09:40:01 GMT
Message-Id: <201301090940.r099e1E0009766@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: MD <mark+freebsdpr@internecto.net>
Subject: Re: kern/164763: Memory leak in VNET
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: MD <mark+freebsdpr@internecto.net>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 09:40:01 -0000

The following reply was made to PR kern/164763; it has been noted by GNATS.

From: MD <mark+freebsdpr@internecto.net>
To: bug-followup@FreeBSD.org, phk@critter.freebsd.dk
Cc:  
Subject: Re: kern/164763: Memory leak in VNET
Date: Wed, 9 Jan 2013 10:20:44 +0100

 Our current rule of thumb is "if you need to shutdown one vimage jail
 then you need to reboot the host."
 
 So we just shut down the services in each jail, leave the jails
 themselves up, and just reboot the host.
 
 Of course this is far from optimal. Is this PR still on the radar of
 anyone?