• KOSAKI Motohiro's avatar
    In a typical oom analysis scenario, we frequently want to know whether the · 610a143d
    KOSAKI Motohiro authored
    killed process has a memory leak or not at the first step.  This patch
    adds vsz and rss information to the oom log to help this analysis.  To
    save time for the debugging.
    
    example:
    ===================================================================
    rsyslogd invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0
    Pid: 1308, comm: rsyslogd Not tainted 2.6.32-rc6 #24
    Call Trace:
    [<ffffffff8132e35b>] ?_spin_unlock+0x2b/0x40
    [<ffffffff810f186e>] oom_kill_process+0xbe/0x2b0
    
    (snip)
    
    492283 pages non-shared
    Out of memory: kill process 2341 (memhog) score 527276 or a child
    Killed process 2341 (memhog) vsz:1054552kB, anon-rss:970588kB, file-rss:4kB
    ===========================================================================
                                 ^
                                 |
                                here
    Signed-off-by: default avatarKOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
    Cc: David Rientjes <rientjes@google.com>
    Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
    610a143d
oom_kill.c 16.9 KB