Re: decode GFP flags in oom killer output.

[David Rientjes]

On Wed, 7 Mar 2012, Dave Jones wrote:

> Decoding these flags by hand in oom reports is tedious,
> and error-prone.
> 

Something like this is already done in include/trace/events/gfpflags.h so 
there should be a generic version of this or something you can already 
use.

The problem here is that you have to allocate an additional 80-bytes for 
the string and the oom killer is notorious for being called deep in the 
stack and you can't statically allocate a string buffer without adding 
additional syncronization.
--
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/