From: David Rientjes <rientjes@google.com>
To: Aaditya Kumar <aaditya.kumar.30@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, kosaki.motohiro@jp.fujitsu.com,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
Mel Gorman <mel@csn.ul.ie>,
akpm@linux-foundation.org, Minchan Kim <minchan.kim@gmail.com>,
takamori.yamaguchi@jp.sony.com, takuzo.ohara@ap.sony.com,
amit.agarwal@ap.sony.com, tim.bird@am.sony.com,
frank.rowand@am.sony.com, kan.iibuchi@jp.sony.com,
aaditya.kumar@ap.sony.com
Subject: Re: [PATCH] mm: bugfix: set current->reclaim_state to NULL while returning from kswapd()
Date: Mon, 5 Nov 2012 13:44:32 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1211051342240.5296@chino.kir.corp.google.com> (raw)
In-Reply-To: <CAEtiSasbEXUeFwCNO09nT8TsEzLF-zZVyJ_pCO9V49hDPbpbAQ@mail.gmail.com>
On Tue, 6 Nov 2012, Aaditya Kumar wrote:
> From: Takamori Yamaguchi <takamori.yamaguchi@jp.sony.com>
>
> 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 off lining,
> __free_slab() can access dangling pointer of current->reclaim_state.
>
It's __free_slab() for slub and kmem_freepages() for slab.
> 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>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-11-05 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 20:13 Aaditya Kumar
2012-11-05 21:44 ` David Rientjes [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1211051342240.5296@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=aaditya.kumar.30@gmail.com \
--cc=aaditya.kumar@ap.sony.com \
--cc=akpm@linux-foundation.org \
--cc=amit.agarwal@ap.sony.com \
--cc=frank.rowand@am.sony.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kan.iibuchi@jp.sony.com \
--cc=kosaki.motohiro@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=minchan.kim@gmail.com \
--cc=takamori.yamaguchi@jp.sony.com \
--cc=takuzo.ohara@ap.sony.com \
--cc=tim.bird@am.sony.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox