summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorTim Bird <tim.bird@am.sony.com>2012-05-31 16:26:16 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2012-05-31 17:49:28 -0700
commit168eeccbc956d2ec083c3a513f7706784ee0dc5f (patch)
tree6fb95d3080fadd96ea37b0e8c1bd747a183f8f60 /kernel
parent43e13cc107cf6cd3c15fbe1cef849435c2223d50 (diff)
downloadop-kernel-dev-168eeccbc956d2ec083c3a513f7706784ee0dc5f.zip
op-kernel-dev-168eeccbc956d2ec083c3a513f7706784ee0dc5f.tar.gz
stack usage: add pid to warning printk in check_stack_usage
In embedded systems, sometimes the same program (busybox) is the cause of multiple warnings. Outputting the pid with the program name in the warning printk helps distinguish which instances of a program are using the stack most. This is a small patch, but useful. Signed-off-by: Tim Bird <tim.bird@am.sony.com> Cc: Oleg Nesterov <oleg@redhat.com> Cc: Frederic Weisbecker <fweisbec@gmail.com> Cc: Andrea Arcangeli <aarcange@redhat.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel')
-rw-r--r--kernel/exit.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/kernel/exit.c b/kernel/exit.c
index 3281493..6d85655 100644
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -884,9 +884,9 @@ static void check_stack_usage(void)
spin_lock(&low_water_lock);
if (free < lowest_to_date) {
- printk(KERN_WARNING "%s used greatest stack depth: %lu bytes "
- "left\n",
- current->comm, free);
+ printk(KERN_WARNING "%s (%d) used greatest stack depth: "
+ "%lu bytes left\n",
+ current->comm, task_pid_nr(current), free);
lowest_to_date = free;
}
spin_unlock(&low_water_lock);
OpenPOWER on IntegriCloud