From owner-freebsd-current Sun Mar 24 9:10:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id A5BB137B419; Sun, 24 Mar 2002 09:10:50 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g2OHAYp1062767; Sun, 24 Mar 2002 18:10:34 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson Cc: "M. Warner Losh" , current@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default In-Reply-To: Your message of "Sun, 24 Mar 2002 12:04:29 EST." Date: Sun, 24 Mar 2002 18:10:34 +0100 Message-ID: <62766.1016989834@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Robe rt Watson writes: >A few weeks ago, I would have believed you. Except that using -J was a >workaround recommended in a recent security advisory--prior to >recommending it, I ran it on a server of mine for a few days. You'd be >surprised how many random applications keel over, and the performance >impact it has for some specific types of applications. No, I will not be surprised no matter what you tell me. I used to keep save all emails I got about phkmalloc nailing bugs, now I only track "significant" ones. But let me turn it around, what would it take for you to accept AJ in the developer release ? Better diagnostics ? -- 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message