Date: Mon, 14 May 2007 00:09:30 +0200 From: Ivan Voras <ivoras@fer.hr> To: Alfred Perlstein <alfred@freebsd.org> Cc: freebsd-arch@freebsd.org Subject: Re: HEADS DOWN Message-ID: <46478C9A.9050807@fer.hr> In-Reply-To: <20070513215442.GZ21795@elvis.mu.org> References: <20070512153532.GQ21795@elvis.mu.org> <63984.1178992555@critter.freebsd.dk> <f25m78$ik$2@sea.gmane.org> <20070513215442.GZ21795@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC64C28F94A354F261EECD2E5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Alfred Perlstein wrote: > Let's clear the issue here... FreeBSD did not have a choice in the > matter. Actually it did. The SIGABORT codepath was only executed in case the process is running under uid=3D0, in other cases it would just print out the warning. I think behaviour such as this is a violation of POLA as the behaviour is different depending on which users runs it (and if the allocator can clearly handle the situation for nonprivileged users, it can also handle it for root, but instead chose to be annoying). > We can't be "bug for bug tolerant" with Linnex without copying > their allocator. =20 No, but we can with the documented parts, and malloc-inside-signal-handler support is documented (http://www.cs.utah.edu/dept/old/texinfo/glibc-manual-0.02/library_toc.ht= ml#SEC357). Even if it's forbidden by POSIX or other standards, FreeBSD isn't popular enough to be one of the systems that don't support it. (This being said, since I'm not going to create a malloc implementation any time soon, it of course depends on the particular author what will or will not be supported :) ). > And since our allocator is vastly superior phkmalloc isn't any more and it remains to be seen for jemalloc :) --------------enigC64C28F94A354F261EECD2E5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGR4ygldnAQVacBcgRAnPCAKCSVQ05vdceGu6NzeIgt5p34sAqKgCeLQvb +QQvUEuYizSSTvSr849/NaU= =zUMD -----END PGP SIGNATURE----- --------------enigC64C28F94A354F261EECD2E5--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46478C9A.9050807>