Date: Sat, 12 May 2007 17:55:55 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Alfred Perlstein <alfred@freebsd.org> Cc: Daniel Eischen <deischen@freebsd.org>, arch@freebsd.org, Robert Watson <rwatson@freebsd.org>, "Sean C. Farley" <sean-freebsd@farley.org> Subject: Re: HEADS DOWN Message-ID: <63984.1178992555@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 12 May 2007 08:35:32 MST." <20070512153532.GQ21795@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20070512153532.GQ21795@elvis.mu.org>, Alfred Perlstein writes: >* Robert Watson <rwatson@FreeBSD.org> [070512 08:11] wrote: >> >> >> Actually, I'm not convinced that crashing the program isn't the right >> answer. If an application corrupts memory managed by libc or other >> libraries, crashing is generally considered an entirely acceptable failure >> mode. > >Phk malloc has said otherwise for the past ... 10 years? > >I like how phk malloc has it as an option. But notice that it is not an option for programs that runs as root or setuid/setgid etc. Given the hostility of networks, I would support a more hardcore attitude to memory mismanagement these days. -- 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?63984.1178992555>