Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261188AbUKCAsL (ORCPT ); Tue, 2 Nov 2004 19:48:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261252AbUKCAoy (ORCPT ); Tue, 2 Nov 2004 19:44:54 -0500 Received: from e34.co.us.ibm.com ([32.97.110.132]:11512 "EHLO e34.co.us.ibm.com") by vger.kernel.org with ESMTP id S261724AbUKBWWh (ORCPT ); Tue, 2 Nov 2004 17:22:37 -0500 Message-ID: <4188086F.8010005@us.ibm.com> Date: Tue, 02 Nov 2004 14:21:35 -0800 From: Dave Hansen User-Agent: Mozilla Thunderbird 0.8 (X11/20040926) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrea Arcangeli CC: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andi Kleen , Andrew Morton Subject: Re: fix iounmap and a pageattr memleak (x86 and x86-64) References: <4187FA6D.3070604@us.ibm.com> <20041102220720.GV3571@dualathlon.random> In-Reply-To: <20041102220720.GV3571@dualathlon.random> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 633 Lines: 13 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/