The patch titled
Subject: kernel/exit.c: quieten greatest stack depth printk
has been added to the -mm tree. Its filename is
exit-quieten-greatest-stack-depth-printk.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/exit-quieten-greatest-stack-depth-printk.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/exit-quieten-greatest-stack-depth-printk.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Anton Blanchard <anton@xxxxxxxxx>
Subject: kernel/exit.c: quieten greatest stack depth printk
Many targets enable CONFIG_DEBUG_STACK_USAGE, and while the information
is useful, it isn't worthy of pr_warn(). Reduce it to pr_info().
Link: http://lkml.kernel.org/r/1466982072-29836-1-git-send-email-anton@xxxxxxxxxx
Signed-off-by: Anton Blanchard <anton@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
kernel/exit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN kernel/exit.c~exit-quieten-greatest-stack-depth-printk kernel/exit.c
--- a/kernel/exit.c~exit-quieten-greatest-stack-depth-printk
+++ a/kernel/exit.c
@@ -639,7 +639,7 @@ static void check_stack_usage(void)
spin_lock(&low_water_lock);
if (free < lowest_to_date) {
- pr_warn("%s (%d) used greatest stack depth: %lu bytes left\n",
+ pr_info("%s (%d) used greatest stack depth: %lu bytes left\n",
current->comm, task_pid_nr(current), free);
lowest_to_date = free;
}
_
Patches currently in -mm which might be from anton@xxxxxxxxx are
exit-quieten-greatest-stack-depth-printk.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
