From owner-freebsd-bugs Tue Apr 2 0:19:28 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6D54337B41C; Tue, 2 Apr 2002 00:19:25 -0800 (PST) Received: (from dillon@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g328JPJ21423; Tue, 2 Apr 2002 00:19:25 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Apr 2002 00:19:25 -0800 (PST) From: Message-Id: <200204020819.g328JPJ21423@freefall.freebsd.org> To: dillon@FreeBSD.org, freebsd-bugs@FreeBSD.org, dillon@FreeBSD.org Subject: Re: kern/36504: crash/panic vm_object_allocate under file system code w/fix Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: crash/panic vm_object_allocate under file system code w/fix Responsible-Changed-From-To: freebsd-bugs->dillon Responsible-Changed-By: dillon Responsible-Changed-When: Tue Apr 2 00:16:47 PST 2002 Responsible-Changed-Why: I'll look at this later on tuesday. It makes sense to have a defensive check but I need more information on the failure case itself. i.e. is it when the zalloc area runs out of VM or is it a temporary, recoverable no-free-pages condition? http://www.freebsd.org/cgi/query-pr.cgi?pr=36504 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message