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)
committerPaul Gortmaker <paul.gortmaker@windriver.com>
Mon, 10 Feb 2014 21:11:09 +0000 (16:11 -0500)
commitf0db044d2f407c9f4f058d5528e66e52fe1be2af
treea2a6eed9b5bad3e6bc2635c1c545f4fe7e181c2b
parente440541697f4343ee06384c693d1904005735120
mm: bugfix: set current->reclaim_state to NULL while returning from kswapd()

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: Paul Gortmaker <paul.gortmaker@windriver.com>
mm/vmscan.c