From owner-freebsd-current@FreeBSD.ORG Wed Nov 30 14:40:12 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA1EC16A420 for ; Wed, 30 Nov 2005 14:40:12 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (nagual.pp.ru [194.87.13.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id C938543D5E for ; Wed, 30 Nov 2005 14:40:11 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.4/8.13.4) with ESMTP id jAUEe01M043151; Wed, 30 Nov 2005 17:40:00 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.4/8.13.4/Submit) id jAUEe0hO043148; Wed, 30 Nov 2005 17:40:00 +0300 (MSK) (envelope-from ache) Date: Wed, 30 Nov 2005 17:39:59 +0300 From: Andrey Chernov To: Jason Evans Message-ID: <20051130143959.GA43118@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Jason Evans , Ulrich Spoerlein , freebsd-current@FreeBSD.ORG References: <6861.1133349506@critter.freebsd.dk> <200511302252.05741.doconnor@gsoft.com.au> <20051130123019.GA1068@galgenberg.net> <820D3D1C-353C-40EC-9D75-75446517A422@canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <820D3D1C-353C-40EC-9D75-75446517A422@canonware.com> User-Agent: Mutt/1.5.11 Cc: freebsd-current@FreeBSD.ORG Subject: Re: New libc malloc patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Nov 2005 14:40:12 -0000 On Wed, Nov 30, 2005 at 06:32:54AM -0800, Jason Evans wrote: > In a previous version of the patch, I included compile-time support > for redzones around allocations. Kris Kennaway did a full ports tree > build with redzones enabled, and several ports caused redzone > corruption, but in every case it was due to writing one byte past the > end of an allocation. None of these were serious, since word > alignment required that the "corrupted" byte be unused. I suspect > that we would catch very few serious errors, even if redzones were > enabled by default. You can make red zones word-aligned in addition to byte-aligned variant, both as malloc options, of course. -- http://ache.pp.ru/