Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753623AbZFOXyE (ORCPT ); Mon, 15 Jun 2009 19:54:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751208AbZFOXxz (ORCPT ); Mon, 15 Jun 2009 19:53:55 -0400 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:41290 "EHLO fgwmail6.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751179AbZFOXxy (ORCPT ); Mon, 15 Jun 2009 19:53:54 -0400 Date: Tue, 16 Jun 2009 08:52:22 +0900 From: KAMEZAWA Hiroyuki To: Wu Fengguang Cc: Andrew Morton , LKML , Andi Kleen , Ingo Molnar , Mel Gorman , Thomas Gleixner , "H. Peter Anvin" , Peter Zijlstra , Nick Piggin , Hugh Dickins , Andi Kleen , "riel@redhat.com" , "chris.mason@oracle.com" , "linux-mm@kvack.org" Subject: Re: [PATCH 10/22] HWPOISON: check and isolate corrupted free pages v2 Message-Id: <20090616085222.1545cc05.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: <20090615101620.GA7216@localhost> References: <20090615024520.786814520@intel.com> <20090615031253.715406280@intel.com> <20090615184112.ed8e2f03.kamezawa.hiroyu@jp.fujitsu.com> <20090615101620.GA7216@localhost> Organization: FUJITSU Co. LTD. X-Mailer: Sylpheed 2.5.0 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2848 Lines: 85 On Mon, 15 Jun 2009 18:16:20 +0800 Wu Fengguang wrote: > On Mon, Jun 15, 2009 at 05:41:12PM +0800, KAMEZAWA Hiroyuki wrote: > > On Mon, 15 Jun 2009 10:45:30 +0800 > > Wu Fengguang wrote: > > > > > From: Wu Fengguang > > > > > > If memory corruption hits the free buddy pages, we can safely ignore them. > > > No one will access them until page allocation time, then prep_new_page() > > > will automatically check and isolate PG_hwpoison page for us (for 0-order > > > allocation). > > > > > > This patch expands prep_new_page() to check every component page in a high > > > order page allocation, in order to completely stop PG_hwpoison pages from > > > being recirculated. > > > > > > Note that the common case -- only allocating a single page, doesn't > > > do any more work than before. Allocating > order 0 does a bit more work, > > > but that's relatively uncommon. > > > > > > This simple implementation may drop some innocent neighbor pages, hopefully > > > it is not a big problem because the event should be rare enough. > > > > > > This patch adds some runtime costs to high order page users. > > > > > > [AK: Improved description] > > > > > > v2: Andi Kleen: > > > Port to -mm code > > > Move check into separate function. > > > Don't dump stack in bad_pages for hwpoisoned pages. > > > > > > Signed-off-by: Wu Fengguang > > > Signed-off-by: Andi Kleen > > > > > > --- > > > mm/page_alloc.c | 20 +++++++++++++++++++- > > > 1 file changed, 19 insertions(+), 1 deletion(-) > > > > > > --- sound-2.6.orig/mm/page_alloc.c > > > +++ sound-2.6/mm/page_alloc.c > > > @@ -233,6 +233,12 @@ static void bad_page(struct page *page) > > > static unsigned long nr_shown; > > > static unsigned long nr_unshown; > > > > > > + /* Don't complain about poisoned pages */ > > > + if (PageHWPoison(page)) { > > > + __ClearPageBuddy(page); > > > + return; > > > + } > > > > Hmm ? why __ClearPageBuddy() is necessary ? > > Because this page is considered to be "allocated" out of the buddy > system, even though we fail the allocation here. > > The page is now owned by no one, especially not owned by the buddy > allocator. > I just wonder "why __ClearPageBuddy() is necessary." When bad_page() is called, a page is removed from buddy allocator and no PG_buddy flag at all....I'm sorry if you added bad_page() caller in buddy allocator. Buddy Allocator I call here is just 2 functions. - __free_one_page() - expand() Bye, -Kame > Thanks, > Fengguang > -- 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/