From owner-freebsd-net@FreeBSD.ORG Sat Jan 17 01:00:15 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABC94106566B for ; Sat, 17 Jan 2009 01:00:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9B1818FC14 for ; Sat, 17 Jan 2009 01:00:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0H10534047006 for ; Sat, 17 Jan 2009 01:00:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0H105sr047005; Sat, 17 Jan 2009 01:00:05 GMT (envelope-from gnats) Date: Sat, 17 Jan 2009 01:00:05 GMT Message-Id: <200901170100.n0H105sr047005@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: "Jason DiCioccio" Cc: Subject: Re: kern/130059: [panic] Leaking 50k mbufs/hour X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jason DiCioccio List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2009 01:00:15 -0000 The following reply was made to PR kern/130059; it has been noted by GNATS. From: "Jason DiCioccio" To: bug-followup@freebsd.org Cc: Subject: Re: kern/130059: [panic] Leaking 50k mbufs/hour Date: Fri, 16 Jan 2009 16:51:47 -0800 I narrowed this bug down to the following patch to djb's ucspi-tcp (adds ipv6 functionality): http://www.fefe.de/ucspi/ I don't think that userland processes should be able to wreak that much havoc on the network stack. Another thing of note is that even if I kill the processes causing the problem, the mbufs are never reclaimed. Seems like a permanent leak. When I got rid of the ipv6 patch, the mbufs stopped building up and everything has been fine.. Note that the ipv6 traffic for this process was fairly minimal.