From owner-freebsd-stable@FreeBSD.ORG Tue Feb 27 21:09:45 2007 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5187316A406 for ; Tue, 27 Feb 2007 21:09:45 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 40DFF13C4BB for ; Tue, 27 Feb 2007 21:09:45 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 1F4441A4D81; Tue, 27 Feb 2007 13:09:45 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 470925138A; Tue, 27 Feb 2007 16:09:44 -0500 (EST) Date: Tue, 27 Feb 2007 16:09:44 -0500 From: Kris Kennaway To: Mikhail Teterin Message-ID: <20070227210943.GA56889@xor.obsecurity.org> References: <200702271059.09230@aldan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200702271059.09230@aldan> User-Agent: Mutt/1.4.2.2i Cc: stable@FreeBSD.org Subject: Re: panic: kmem_malloc(16384): kmem_map too small: md-mounted /tmp filled up X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2007 21:09:45 -0000 Documented in the manpage, use swap backing or reserve enough space. Kris On Tue, Feb 27, 2007 at 10:59:08AM -0500, Mikhail Teterin wrote: > The memory-mounted /tmp filled up on this 6.2-PRERELEASE system (as of Nov 7). > > Unfortunately, instead of the process existing due to ENOSPC, the entire > system paniced: > > [...] > g_vfs_done():md0[WRITE(offset=982335488, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=982466560, length=131072)]error = 28 > panic: kmem_malloc(16384): kmem_map too small: 259153920 total allocated > Uptime: 34d21h13m21s > Dumping 767 MB (2 chunks) > chunk 0: 1MB (159 pages) ... ok > chunk 1: 767MB (196288 pages) 751 735 719 703 687 671 655 639 623 607 591 > 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 > 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 ... ok > > Dump complete > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... > > I don't think, such DoS-ing is normal -- a regular user shot the entire system > in the knee... > > Is anybody interested in the stack/etc.? Is this something, that's fixed in > the more recent 6.2? > > Machine has 3/4Gb RAM and ample swap: > > Device 1K-blocks Used Avail Capacity > /dev/ad0s1b 3145728 32 3145696 0% > /dev/ad2s1b 1048576 32 1048544 0% > Total 4194304 64 4194240 0% > > /tmp's space allocation (after reboot) is as follows: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/md0 2026030 3552 1860396 0% /tmp > > Note, that it is supposed to hold 2Gb, but was filled up and paniced holding > about 300Mb... Probably, because it is created with ``-M'' by default -- but > it is not supposed to panic anyway! > > Please, advise. Thanks! > > -mi > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >