From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 2 Nov 2004 14:29:44 -0800 From: Andrew Morton Subject: Re: fix iounmap and a pageattr memleak (x86 and x86-64) Message-Id: <20041102142944.0be6f750.akpm@osdl.org> In-Reply-To: <4188086F.8010005@us.ibm.com> References: <4187FA6D.3070604@us.ibm.com> <20041102220720.GV3571@dualathlon.random> <4188086F.8010005@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Dave Hansen Cc: andrea@novell.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, ak@suse.de List-ID: Dave Hansen wrote: > > Andrea Arcangeli wrote: > > Still I recommend investigating _why_ debug_pagealloc is violating the > > API. It might not be necessary to wait for the pageattr universal > > feature to make DEBUG_PAGEALLOC work safe. > > OK, good to know. But, for now, can we pull this out of -mm? Or, at > least that BUG_ON()? DEBUG_PAGEALLOC is an awfully powerful debugging > tool to just be removed like this. If we make it a WARN_ON, will that cause a complete storm of output? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org