Re: [patch] oom: give current access to memory reserves if it hasbeen killed
From: Oleg Nesterov
Date: Fri Apr 02 2010 - 07:17:07 EST
On 04/01, David Rientjes wrote:
> On Thu, 1 Apr 2010, Oleg Nesterov wrote:
> > > You can't do this for the reason I cited in another email, oom_badness()
> > > returning 0 does not exclude a task from being chosen by
> > > selcet_bad_process(), it will use that task if nothing else has been found
> > > yet. We must explicitly filter it from consideration by checking for
> > > !p->mm.
> > Yes, you are right. OK, oom_badness() can never return points < 0,
> > we can make it int and oom_badness() can return -1 if !mm. IOW,
> > - unsigned int points;
> > + int points;
> > ...
> > points = oom_badness(...);
> > if (points >= 0 && (points > *ppoints || !chosen))
> > chosen = p;
> oom_badness() and its predecessor badness() in mainline never return
> negative scores, so I don't see the value in doing this; just filter the
> task in select_bad_process() with !p->mm as it has always been done.
David, you continue to ignore my arguments ;) select_bad_process()
must not filter out the tasks with ->mm == NULL.
void *memory_hog_thread(void *arg)
Now, even if we fix PF_EXITING check, select_bad_process() will always
ignore this process. The group leader has ->mm == NULL.
That is why I think we need something like find_lock_task_mm() in the
pseudo-patch I sent.
Or I missed something?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/