> The oom killer header, including information such as the allocation order> and gfp mask, current's cpuset and memory controller, call trace, and VM> state information is currently only shown when the oom killer has> selected a task to kill.> > This information is omitted, however, when the oom killer panics either> because of panic_on_oom sysctl settings or when no killable task was> found. It is still relevant to know crucial pieces of information such> as the allocation order and VM state when diagnosing such issues,> especially at boot.> > This patch displays the oom killer header whenever it panics so that bug> reports can include pertinent information to debug the issue, if> possible.> > Signed-off-by: David Rientjes <rientjes@google.com>