mm/oom_kill.c: fix task_will_free_mem() comment
authorMichal Hocko <mhocko@kernel.org>
Fri, 7 Oct 2016 23:57:32 +0000 (16:57 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Sat, 8 Oct 2016 01:46:26 +0000 (18:46 -0700)
Attempt to demystify the task_will_free_mem() loop.

Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
mm/oom_kill.c

index ef175518f05f2d24df08e217354a56b17c8e1c08..463cdd22d4e0df8e1834330e058ab37c69bb2273 100644 (file)
@@ -803,8 +803,9 @@ static bool task_will_free_mem(struct task_struct *task)
                return true;
 
        /*
-        * This is really pessimistic but we do not have any reliable way
-        * to check that external processes share with our mm
+        * Make sure that all tasks which share the mm with the given tasks
+        * are dying as well to make sure that a) nobody pins its mm and
+        * b) the task is also reapable by the oom reaper.
         */
        rcu_read_lock();
        for_each_process(p) {