Re: cc1plus invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0

From: KOSAKI Motohiro
Date: Wed Nov 04 2009 - 18:20:33 EST


> > + if (verbose) {
> > + task_lock(p);
>
> We need to be careful with which locks we take on the oom-killer path,
> because it can be called by code which already holds locks. But I
> expect task_lock() will be OK.

Sure.
task_lock() is already used various oom path. I think this is ok.



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