From: Hugh Dickins From: Andrea Arcangeli page_alloc.c's bad_page routine should reset a bad mapcount; and it's more revealing to show the bad mapcount than just the boolean mapped. --- 25-akpm/mm/page_alloc.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff -puN mm/page_alloc.c~rmap-30-fix-bad-mapcount mm/page_alloc.c --- 25/mm/page_alloc.c~rmap-30-fix-bad-mapcount 2004-05-08 21:56:25.752262056 -0700 +++ 25-akpm/mm/page_alloc.c 2004-05-08 21:56:25.756261448 -0700 @@ -73,9 +73,9 @@ static void bad_page(const char *functio { printk(KERN_EMERG "Bad page state at %s (in process '%s', page %p)\n", function, current->comm, page); - printk(KERN_EMERG "flags:0x%08lx mapping:%p mapped:%d count:%d\n", + printk(KERN_EMERG "flags:0x%08lx mapping:%p mapcount:%d count:%d\n", (unsigned long)page->flags, page->mapping, - page_mapped(page), page_count(page)); + (int)page->mapcount, page_count(page)); printk(KERN_EMERG "Backtrace:\n"); dump_stack(); printk(KERN_EMERG "Trying to fix it up, but a reboot is needed\n"); @@ -90,6 +90,7 @@ static void bad_page(const char *functio 1 << PG_writeback); set_page_count(page, 0); page->mapping = NULL; + page->mapcount = 0; } #ifndef CONFIG_HUGETLB_PAGE _