From owner-freebsd-stable@FreeBSD.ORG  Fri May 26 10:26:40 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 67ED416A47B
	for <freebsd-stable@freebsd.org>; Fri, 26 May 2006 10:26:40 +0000 (UTC)
	(envelope-from tbyte@otel.net)
Received: from mail.otel.net (gw3.OTEL.net [212.36.8.151])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AAFE543D55
	for <freebsd-stable@freebsd.org>; Fri, 26 May 2006 10:26:37 +0000 (GMT)
	(envelope-from tbyte@otel.net)
Received: from dragon.otel.net ([212.36.8.135])
	by mail.otel.net with esmtp (Exim 4.60 (FreeBSD))
	(envelope-from <tbyte@otel.net>)
	id 1FjZWT-000Pm6-Ck; Fri, 26 May 2006 13:26:26 +0300
From: Iasen Kostov <tbyte@otel.net>
To: Kris Kennaway <kris@obsecurity.org>
In-Reply-To: <20060525205414.GC30137@xor.obsecurity.org>
References: <wpy7wq6qlh.fsf@heho.labo>
	<20060525205414.GC30137@xor.obsecurity.org>
Content-Type: text/plain
Date: Fri, 26 May 2006 13:26:24 +0300
Message-Id: <1148639184.78660.32.camel@DraGoN.OTEL.net>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org
Subject: Re: kmem leak in tmpmfs?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 May 2006 10:26:41 -0000

On Thu, 2006-05-25 at 16:54 -0400, Kris Kennaway wrote:
> On Thu, May 25, 2006 at 06:01:30PM +0200, Arno J. Klaassen wrote:
> > Hello,
> > 
> > I get a very easy to reproduce panic on 6.1-STABLE :
> > 
> > /etc/periodic/weekly/310.locate panics with
> > 
> >   panic: kmem_malloc(4096): kmem_map too small: 335544320 total allocated
> 
> It looks like you are using a malloc-backed md and you do not have
> enough RAM to handle the size.  Perhaps tmpmfs does not use swap
> backing, as it is supposed to?
> 
> Kris

	First of all if there is not enough kmem (not just plain ram I think)
kernel should not allow disk creation in first place, second - I think
(although there could be some ... reason for that) it's stupid way to
say "I don't have more kmem" by panicing :). Better way will be just to
fail disk operation of that FS with "Disk is full" or something like
that. At home I tried to raise kmem like that:
"vm.kmem_size_max="1073741824" (I got 2G of RAM)
(setting vm.kmem_size directly panices kernel at boot if I remember
correctly).

but for my surprise kernel panices at exact same allocated md disk space
with the same panic as the original poster's. Is it possible that I
should rise KVA_PAGES too ? And I don't think its documented anywhere
(of course I've tried googling and it's always possible that I've missed
something :). All this was on FreeBSD 6.0.