From owner-freebsd-bugs@FreeBSD.ORG Tue Mar 1 06:20:16 2005 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E74D16A4CE for ; Tue, 1 Mar 2005 06:20:16 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id F224F43D49 for ; Tue, 1 Mar 2005 06:20:15 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j216KFbs007309 for ; Tue, 1 Mar 2005 06:20:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j216KFu3007308; Tue, 1 Mar 2005 06:20:15 GMT (envelope-from gnats) Resent-Date: Tue, 1 Mar 2005 06:20:15 GMT Resent-Message-Id: <200503010620.j216KFu3007308@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Yar Tikhiy Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93CC016A4CE for ; Tue, 1 Mar 2005 06:18:34 +0000 (GMT) Received: from bsd.chem.msu.ru (bsd.chem.msu.ru [195.208.208.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4C5943D41 for ; Tue, 1 Mar 2005 06:18:33 +0000 (GMT) (envelope-from yar@bsd.chem.msu.ru) Received: from bsd.chem.msu.ru (localhost [127.0.0.1]) by bsd.chem.msu.ru (8.13.1/8.13.1) with ESMTP id j216IWaR071305 for ; Tue, 1 Mar 2005 09:18:32 +0300 (MSK) (envelope-from yar@bsd.chem.msu.ru) Received: (from yar@localhost) by bsd.chem.msu.ru (8.13.1/8.13.1/Submit) id j216IVQS071304; Tue, 1 Mar 2005 09:18:31 +0300 (MSK) (envelope-from yar) Message-Id: <200503010618.j216IVQS071304@bsd.chem.msu.ru> Date: Tue, 1 Mar 2005 09:18:31 +0300 (MSK) From: Yar Tikhiy To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: kern/78227: Destroying a network interface leaks kernel memory X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2005 06:20:16 -0000 >Number: 78227 >Category: kern >Synopsis: Destroying a network interface leaks kernel memory >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Mar 01 06:20:15 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Yar Tikhiy >Release: FreeBSD 6.0-CURRENT i386 >Organization: MSU >Environment: 5-STABLE, 6-CURRENT >Description: It was originally reported by Oleg Bulyzhin rinet <.> ru> that destroying a vlan(4) interface with an assigned IP address would leak kernel memory. Further investigation has shown that the problem isn't specific to vlan(4) and affects any multicast interface. The system just doesn't seem to leave the "all hosts" multicast group upon dismantling an interface. In my case, each plumb/unplumb cycle on a vlan(4) interface leaks 1 in_multi memory block and 5 ether_multi blocks. For lo(4) the amounts are 1 and 2, respectively. >How-To-Repeat: # change lo11 to vlanXX and add vlan/vlandev to the create command to test on vlan vmstat -m > vmstat-m.0 for n in `yes | head -1000`; do ifconfig lo11 create inet 1.1.1.1/24 up ifconfig lo11 destroy done vmstat -m > vmstat-m.1 diff vmstat-m.0 vmstat-m.1 >Fix: >Release-Note: >Audit-Trail: >Unformatted: