Messages in this thread | | | Date | Thu, 7 Jan 2016 13:29:11 -0800 (PST) | From | David Rientjes <> | Subject | Re: [PATCH v2 9/9] mm, oom: print symbolic gfp_flags in oom warning |
| |
On Tue, 24 Nov 2015, Vlastimil Babka wrote:
> It would be useful to translate gfp_flags into string representation when > printing in case of an OOM, especially as the flags have been undergoing some > changes recently and the script ./scripts/gfp-translate needs a matching source > version to be accurate. > > Example output: > > a.out invoked oom-killer: order=0, oom_score_adj=0, gfp_mask=0x24280ca(GFP_HIGHUSER_MOVABLE|GFP_ZERO) >
Is there a way that we can keep the order of the fields so that anything parsing the kernel log for oom kills doesn't break? The messages printed to the kernel log are the only (current) way to determine that the kernel killed something so we should be careful not to break anything parsing them, and this is a common line to look for.
| |