From owner-freebsd-arch@FreeBSD.ORG  Sun Sep 12 21:25:17 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A60E416A4CF
	for <arch@freebsd.org>; Sun, 12 Sep 2004 21:25:17 +0000 (GMT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 112FD43D41
	for <arch@freebsd.org>; Sun, 12 Sep 2004 21:25:17 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id i8CLPDQC061287;
	Sun, 12 Sep 2004 23:25:14 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: "M. Warner Losh" <imp@bsdimp.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Sun, 12 Sep 2004 15:20:47 MDT."
             <20040912.152047.16265436.imp@bsdimp.com> 
Date: Sun, 12 Sep 2004 23:25:13 +0200
Message-ID: <61286.1095024313@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: arch@freebsd.org
Subject: Re: [BIKESHED] Giving abort(2) a reason 
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Sep 2004 21:25:17 -0000

In message <20040912.152047.16265436.imp@bsdimp.com>, "M. Warner Losh" writes:
>In message: <61109.1095023635@critter.freebsd.dk>
>            "Poul-Henning Kamp" <phk@phk.freebsd.dk> writes:
>: In message <20040912.142552.83283958.imp@bsdimp.com>, "M. Warner Losh" writes:
>: 
>: >: Given that we are usually pretty stumped when we get to call abort(2)
>: >: it needs to work without malloc or anything like it and varargs into
>: >: the kernel is not at all in my future.
>: >
>: >Only in malloc.  Everywhere else, people have enough state to cope.
>: >Do we really want to have another kernel API just to support malloc
>: >failures?
>: 
>: Well, the problem is that practically nothing else works once malloc
>: fails, and people seem to find the lack of visible explanation a
>: problem.
>: 
>: syslog() or anything else using varargs is not going to work...
>
>Wouldn't it be better to have a more generic 'Put this into dmesg'
>thing that doesn't require malloc to work?  It seems silly to bloat
>the kernel for only a malloc failure case...

That is what I thought I proposed...

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.