tracing: Add BUG_ON when stack end location is over written
authorAaron Tomlin <atomlin@redhat.com>
Mon, 24 Mar 2014 14:03:57 +0000 (14:03 +0000)
committerSteven Rostedt <rostedt@goodmis.org>
Mon, 24 Mar 2014 14:39:11 +0000 (10:39 -0400)
commit3862807880acc0adaef6749738d210c9f45c3049
tree1545044eb873c915f015288fb4b45e5a3bd50a55
parent0dea6d52638b2693b18cd2ed8938b236e0789ddb
tracing: Add BUG_ON when stack end location is over written

It is difficult to detect a stack overrun when it
actually occurs.

We have observed that this type of corruption is often
silent and can go unnoticed. Once the corrupted region
is examined, the outcome is undefined and often
results in sporadic system crashes.

When the stack tracing feature is enabled, let's check
for this condition and take appropriate action.

Note: init_task doesn't get its stack end location
set to STACK_END_MAGIC.

Link: http://lkml.kernel.org/r/1395669837-30209-1-git-send-email-atomlin@redhat.com
Signed-off-by: Aaron Tomlin <atomlin@redhat.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
kernel/trace/trace_stack.c