[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091207053806.GA17052@elte.hu>
Date: Mon, 7 Dec 2009 06:38:06 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Andi Kleen <andi@...stfloor.org>
Cc: Wu Fengguang <fengguang.wu@...el.com>,
Alex Chiang <achiang@...com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"Li, Haicheng" <haicheng.li@...el.com>,
Randy Dunlap <randy.dunlap@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Christoph Lameter <cl@...ux-foundation.org>,
Rik van Riel <riel@...hat.com>, Mel Gorman <mel@....ul.ie>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Subject: Re: [RFC] print symbolic page flag names in bad_page()
* Andi Kleen <andi@...stfloor.org> wrote:
> > So how about this patch?
>
> I like it. Decoding the flags by hand is always a very unpleasant
> experience. Bonus: dump_page can be called from kgdb too.
Guys, please do more review:
> +void dump_page(struct page *page)
> +{
> + char buf[1024];
NAK. This code causes a brutal, +1K kernel stack footprint spike that
can crash a system _precisely_ when we are trying to dump a (presumably
rare) condition.
> +EXPORT_SYMBOL(dump_page);
( Small detail: such exports are EXPORT_SYMBOL_GPL - we dont want random
external modules start using it. )
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists