From owner-freebsd-bugs@FreeBSD.ORG Wed Aug 1 08:50:15 2007 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 679EE16A420 for ; Wed, 1 Aug 2007 08:50:15 +0000 (UTC) (envelope-from magpasikat@yahoo.com) Received: from web44914.mail.sp1.yahoo.com (web44914.mail.sp1.yahoo.com [68.180.197.164]) by mx1.freebsd.org (Postfix) with SMTP id 3127213C483 for ; Wed, 1 Aug 2007 08:50:15 +0000 (UTC) (envelope-from magpasikat@yahoo.com) Received: (qmail 60691 invoked by uid 60001); 1 Aug 2007 08:23:35 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=3E5AzwejzVQpvbelyq8S5aGKmMXdtZAqbIxBq2LPMXMB12MWqfc72zU87WZlTSrnmZqXp0fhw5dzZY6IgyKjmWAwel7SeR7ESesR2afXnZAJrLr5Olre+w8JJGuVcnWVjl0Rkk5JcGgKuMgphuM0RQ801j/IqL5zMRbuHrarLk0=; X-YMail-OSG: de5eefAVM1n3sRhZ_yvxF.XtXDq9l9EAcuC95jTbdmuiddGKtHIUe4xj4gI__HcNJEWu9oeezYeIwqC_ctNoiWbGzD2w_9ENmNY- Received: from [58.71.34.137] by web44914.mail.sp1.yahoo.com via HTTP; Wed, 01 Aug 2007 01:23:35 PDT Date: Wed, 1 Aug 2007 01:23:35 -0700 (PDT) From: Martha Pasikatan To: freebsd-bugs@FreeBSD.org MIME-Version: 1.0 Message-ID: <641966.58948.qm@web44914.mail.sp1.yahoo.com> X-Mailman-Approved-At: Wed, 01 Aug 2007 11:28:43 +0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Fwd: Re: kern/115106: When malloc returns null, function proceeds as if pointer is valid at sigacts_alloc X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Aug 2007 08:50:15 -0000 I don't how to update the bug report. Please tell me. Concerning this bug, the fix is incorrect. The malloc has a flag M_WAITOK so the kernel is panicking because there is no more memory left. I had hoped that there was another way for the system to react to having no more memory aside from this, but apparently this is the design so please just drop this bug report. Thank you for your time, matt FreeBSD-gnats-submit@FreeBSD.org wrote: Date: Wed, 1 Aug 2007 03:40:00 GMT To: "M. Pasikatan" From: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: kern/115106: When malloc returns null, function proceeds as if pointer is valid at sigacts_alloc Thank you very much for your problem report. It has the internal identification `kern/115106'. The individual assigned to look at your report is: freebsd-bugs. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=115106 >Category: kern >Responsible: freebsd-bugs >Synopsis: When malloc returns null, function proceeds as if pointer is valid at sigacts_alloc >Arrival-Date: Wed Aug 01 03:40:00 GMT 2007 --------------------------------- Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool.