mm: bugfix: set current->reclaim_state to NULL while returning from kswapd()
authorTakamori Yamaguchi <takamori.yamaguchi@jp.sony.com>
Thu, 8 Nov 2012 23:53:39 +0000 (15:53 -0800)
committerBen Hutchings <ben@decadent.org.uk>
Fri, 16 Nov 2012 16:47:13 +0000 (16:47 +0000)
commit b0a8cc58e6b9aaae3045752059e5e6260c0b94bc upstream.

In kswapd(), set current->reclaim_state to NULL before returning, as
current->reclaim_state holds reference to variable on kswapd()'s stack.

In rare cases, while returning from kswapd() during memory offlining,
__free_slab() and freepages() can access the dangling pointer of
current->reclaim_state.

Signed-off-by: Takamori Yamaguchi <takamori.yamaguchi@jp.sony.com>
Signed-off-by: Aaditya Kumar <aaditya.kumar@ap.sony.com>
Acked-by: David Rientjes <rientjes@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
mm/vmscan.c

index 86eb848..313381c 100644 (file)
@@ -3015,6 +3015,8 @@ static int kswapd(void *p)
                                                &balanced_classzone_idx);
                }
        }
+
+       current->reclaim_state = NULL;
        return 0;
 }