All of lore.kernel.org
 help / color / mirror / Atom feed
* [patch 3/7] revert "mm: memcontrol: fix possible css ref leak on oom"
@ 2016-06-08 22:33 akpm
  0 siblings, 0 replies; only message in thread
From: akpm @ 2016-06-08 22:33 UTC (permalink / raw)
  To: torvalds, mm-commits, akpm, hannes, mhocko, vdavydov

From: Andrew Morton <akpm@linux-foundation.org>
Subject: revert "mm: memcontrol: fix possible css ref leak on oom"

Revert 1383399d7be02 ("mm: memcontrol: fix possible css ref leak on oom").
Johannes points out "There is a task_in_memcg_oom() check before calling
mem_cgroup_oom()".

Acked-by: Michal Hocko <mhocko@suse.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Vladimir Davydov <vdavydov@virtuozzo.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 mm/memcontrol.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff -puN mm/memcontrol.c~revert-mm-memcontrol-fix-possible-css-ref-leak-on-oom mm/memcontrol.c
--- a/mm/memcontrol.c~revert-mm-memcontrol-fix-possible-css-ref-leak-on-oom
+++ a/mm/memcontrol.c
@@ -1608,7 +1608,7 @@ static void memcg_oom_recover(struct mem
 
 static void mem_cgroup_oom(struct mem_cgroup *memcg, gfp_t mask, int order)
 {
-	if (!current->memcg_may_oom || current->memcg_in_oom)
+	if (!current->memcg_may_oom)
 		return;
 	/*
 	 * We are in the middle of the charge context here, so we
_

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-06-08 22:33 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-08 22:33 [patch 3/7] revert "mm: memcontrol: fix possible css ref leak on oom" akpm

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.