aboutsummaryrefslogtreecommitdiff
path: root/lib/mpi/mpi-cmp.c
diff options
context:
space:
mode:
authorJoel Savitz <[email protected]>2019-09-23 15:37:04 -0700
committerLinus Torvalds <[email protected]>2019-09-24 15:54:10 -0700
commit8ac3f8fe91a2119522a73fbc41d354057054e6ed (patch)
tree862705e6af392df50c3a040268423c810f883c65 /lib/mpi/mpi-cmp.c
parent4406548ee39c2268876b61a927acad45da6f9aef (diff)
mm/oom_kill.c: add task UID to info message on an oom kill
In the event of an oom kill, useful information about the killed process is printed to dmesg. Users, especially system administrators, will find it useful to immediately see the UID of the process. We already print uid when dumping eligible tasks so it is not overly hard to find that information in the oom report. However this information is unavailable when dumping of eligible tasks is disabled. In the following example, abuse_the_ram is the name of a program that attempts to iteratively allocate all available memory until it is stopped by force. Current message: Out of memory: Killed process 35389 (abuse_the_ram) total-vm:133718232kB, anon-rss:129624980kB, file-rss:0kB, shmem-rss:0kB Patched message: Out of memory: Killed process 2739 (abuse_the_ram), total-vm:133880028kB, anon-rss:129754836kB, file-rss:0kB, shmem-rss:0kB, UID:0 [[email protected]: s/UID %d/UID:%u/ in printk] Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Joel Savitz <[email protected]> Suggested-by: David Rientjes <[email protected]> Acked-by: Rafael Aquini <[email protected]> Cc: Michal Hocko <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'lib/mpi/mpi-cmp.c')
0 files changed, 0 insertions, 0 deletions