Re: [PATCH 1/9] oom: don't try to kill oom_unkillable child

[KOSAKI Motohiro]

> On Wed, Jun 16, 2010 at 08:29:13PM +0900, KOSAKI Motohiro wrote:
> > Now, badness() doesn't care neigher CPUSET nor mempolicy. Then
> > if the victim child process have disjoint nodemask, __out_of_memory()
> > can makes kernel hang eventually.
> > 
> > This patch fixes it.
> > 
> > Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx>
> Reviewed-by: Minchan Kim <minchan.kim@xxxxxxxxx>
> 
> This patch inclues two things. 
> 
> 1. consider cpuset and mempolicy in oom_kill_process
> 2. Simplify mempolicy oom check with nodemask != NULL 
>    in select_bad_process.
> 
> 1) change behavior but 2) is just cleanup. 
> It should have been in another patch to reivew easily. :)

Thank you. removed (2).



--
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/