From owner-freebsd-hackers Mon Mar 18 08:01:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA01881 for hackers-outgoing; Mon, 18 Mar 1996 08:01:49 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA01872 for ; Mon, 18 Mar 1996 08:01:45 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id JAA04404; Mon, 18 Mar 1996 09:02:37 -0700 Date: Mon, 18 Mar 1996 09:02:37 -0700 From: Nate Williams Message-Id: <199603181602.JAA04404@rocky.sri.MT.net> To: Luigi Rizzo Cc: hackers@FreeBSD.ORG Subject: Re: CFV: adding phk_malloc to -stable In-Reply-To: <199603180930.KAA00195@labinfo.iet.unipi.it> References: <199603180930.KAA00195@labinfo.iet.unipi.it> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Luigi Rizzo writes: > > Until you can demonstrate that NOTHING is (more) broken by doing so, > > > > I VOTE NO! > > Following this reasoning, you will not allow any extension whatsoever > to the kernel or system libs or other critical parts of the system, > because you often cannot demonstrate what you ask. Actually, we aren't supposed to to be adding extensions to the system or kernel in -stable. However, some things slip through because they are required for critical bug fixes and/or necessary to make life easier and don't affect stability (such as libdisk recently). > A more sensible position would be to ask those who use phkmalloc to > report any brokennes evidenced by the new routine. Broken-ness aside, there is also the appearance of brokeness. Some of the strengths of phkmalloc for a developer are weaknesses to a user. There are still bugs fixed in -current which haven't been brought back into -stable that are revealed by phkmalloc. I've found at least one new one, but I haven't been able to track it down (yet). The appearance of bugs makes people think something is wrong when in fact it might not be. Some of the recent kernel messages are a good example of 'un-necessary' information. Whenever someone sees this message, the user immediately assumes something is wrong when in fact it's an information only message. In the same manner, the messages phkmalloc spits out would only confuse normal users. Finally, it's easy enough for those folks who *know* how to bring it into -stable to bring it in. We're not penalizing folks who have knowledge, simply not enabling it for everyone. Nate