From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail144.messagelabs.com (mail144.messagelabs.com [216.82.254.51]) by kanga.kvack.org (Postfix) with ESMTP id 876836B004D for ; Mon, 29 Jun 2009 06:21:39 -0400 (EDT) Date: Mon, 29 Jun 2009 12:18:19 +0200 From: Johannes Weiner Subject: Re: BUG: Bad page state [was: Strange oopses in 2.6.30] Message-ID: <20090629101819.GA2052@cmpxchg.org> References: <1245686553.7799.102.camel@lts-notebook> <20090622205308.GG3981@csn.ul.ie> <20090623200846.223C.A69D9226@jp.fujitsu.com> <20090629084114.GA28597@csn.ul.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090629084114.GA28597@csn.ul.ie> Sender: owner-linux-mm@kvack.org To: Mel Gorman Cc: KOSAKI Motohiro , Lee Schermerhorn , Jiri Slaby , Maxim Levitsky , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton , Christoph Lameter , Pekka Enberg , Rik van Riel List-ID: On Mon, Jun 29, 2009 at 09:41:14AM +0100, Mel Gorman wrote: > I see the unconditionoal clearing of the flag was merged since but even > that might be too heavy handed as we are making a locked bit operation > on every page free. That's unfortunate overhead to incur on every page > free to handle a situation that should not be occurring at all. Linus was probably quick to merge it as istr several people hitting bad_page() triggering. We should get rid of the locked op, I was just not 100% sure and chose the safer version. > > > + WARN_ONCE(1, KERN_WARNING > > > + "Sloppy page flags set process %s at pfn:%05lx\n" > > > + "page:%p flags:%p\n", > > > + current->comm, page_to_pfn(page), > > > + page, (void *)page->flags); [...] > > > + page->flags &= ~PAGE_FLAGS_WARN_AT_FREE; > > > + } > > > + > > > if (unlikely(page_mapcount(page) | > > > (page->mapping != NULL) | > > > (atomic_read(&page->_count) != 0) | > > > > Howerver, I like this patch concept. this warning is useful and meaningful IMHO. > > > > This is a version that is based on top of current mainline that just > displays the warning. However, I think we should consider changing > TestClearPageMlocked() back to PageMlocked() and only clearing the flags > when the unusual condition is encountered. I have a diff at home that makes this an unlocked __TestClearPageMlocked(), would you be okay with this? -- 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: email@kvack.org