Date: Sun, 24 Mar 2002 18:10:34 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Robert Watson <rwatson@FreeBSD.ORG> Cc: "M. Warner Losh" <imp@village.org>, current@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default Message-ID: <62766.1016989834@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 24 Mar 2002 12:04:29 EST." <Pine.NEB.3.96L.1020324120226.47668f-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.NEB.3.96L.1020324120226.47668f-100000@fledge.watson.org>, 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?62766.1016989834>