bad_page: clear reclaim and slab
Subsystems (2)
PATCH 1/1 bad_page: clear reclaim and slab
Since free_pages_check complains if PG_reclaim or PG_slab is set, bad_page ought to clear them to avoid repetitive reports (Nikita noticed this too). Let prep_new_page check page_count and PG_slab as free_pages_check does.
Signed-off-by Hugh Dickins <[email protected]>
---
mm/page_alloc.c | 15 ++++++++++----- 1 files changed, 10 insertions(+), 5 deletions(-)
mm/page_alloc.c +10 -5
@@ -105,11 +105,13 @@ static void bad_page(const char *functioprintk (KERN_EMERG "Backtrace:\n" );dump_stack ();printk (KERN_EMERG "Trying to fix it up, but a reboot is needed\n" ); - page->flags &= ~(1 << PG_private | + page->flags &= ~(1 << PG_lru | +1 << PG_private |1 << PG_locked | -1 << PG_lru |1 << PG_active |1 << PG_dirty | +1 << PG_reclaim | +1 << PG_slab |1 << PG_swapcache |1 << PG_writeback);set_page_count (page,0 );
@@ -440,14 +442,17 @@ void set_page_refs(struct page *page, in*/ static void prep_new_page (struct page *page,int order) { -if (page->mapping ||page_mapcount (page) || - (page->flags & ( +if (page_mapcount (page) || + page->mapping !=NULL || +page_count (page) !=0 || + (page->flags & ( +1 << PG_lru |1 << PG_private |1 << PG_locked | -1 << PG_lru |1 << PG_active |1 << PG_dirty |1 << PG_reclaim | +1 << PG_slab |1 << PG_swapcache |1 << PG_writeback )))bad_page (__FUNCTION__, page);