From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 285A5DDE1D for ; Sat, 28 Mar 2009 10:06:03 +1100 (EST) Subject: Re: CONFIG_DEBUG_PAGEALLOC generates WARN_ON() in ppc32 hash From: Benjamin Herrenschmidt To: Kumar Gala In-Reply-To: <765C1EA1-93F7-4FEF-930B-78E2B3DEB4FA@kernel.crashing.org> References: <765C1EA1-93F7-4FEF-930B-78E2B3DEB4FA@kernel.crashing.org> Content-Type: text/plain Date: Sat, 28 Mar 2009 10:05:57 +1100 Message-Id: <1238195157.20197.81.camel@pasglop> Mime-Version: 1.0 Cc: LinuxPPC Mailing List List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, 2009-03-27 at 06:56 -0500, Kumar Gala wrote: > Ben, > > If we have CONFIG_DEBUG_PAGEALLOC enabled we end up hitting the > WARN_ON() in set_pte_at() when we boot. This appears because we've > already setup pte's via mapin_ram() after which we end up calling > kernel_map_pages(). > > So I'm not sure if __change_page_attr() should be doing something > different or if the WARN_ON() should be conditional on ! > CONFIG_DEBUG_PAGEALLOC Or use __set_pte_at() ? Note that C_D_P doesn't work on hash32 anyway... Ben.