Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1303923

Re: [PATCH v2 9/9] mm, oom: print symbolic gfp_flags in oom warning

From David Rientjes <rientjes@google.com>
Newsgroups linux.kernel
Subject Re: [PATCH v2 9/9] mm, oom: print symbolic gfp_flags in oom warning
Date 2016-01-07 22:30 +0100
Message-ID <qOqi7-5nl-15@gated-at.bofh.it> (permalink)
References <qyl33-86O-5@gated-at.bofh.it> <qyl34-86O-17@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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.

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

Re: [PATCH v2 9/9] mm, oom: print symbolic gfp_flags in oom  warning David Rientjes <rientjes@google.com> - 2016-01-07 22:30 +0100
  Re: [PATCH v2 9/9] mm, oom: print symbolic gfp_flags in oom warning Vlastimil Babka <vbabka@suse.cz> - 2016-01-08 12:40 +0100

csiph-web