* [PATCH] check for stack overflow in ___might_sleep
@ 2014-12-16 22:25 Eric Sandeen
2015-01-14 14:01 ` [tip:sched/core] sched/debug: Check for stack overflow in ___might_sleep() tip-bot for Eric Sandeen
0 siblings, 1 reply; 2+ messages in thread
From: Eric Sandeen @ 2014-12-16 22:25 UTC (permalink / raw)
To: kernel list, Ingo Molnar, Peter Zijlstra
Sometimes a "BUG: sleeping function called from invalid context"
message is not indicative of locking problems, but is the result
of a stack overflow corrupting the thread info.
Witness http://oss.sgi.com/archives/xfs/2014-02/msg00325.html
for example, which took a few go-rounds to sort out.
If we're printing the warning, things are wonky already, and
it'd be informative to check for the stack end corruption at this
point, too.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index b5797b7..4ef726c 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -7328,6 +7328,9 @@ void ___might_sleep(const char *file, int line, int preempt_offset)
in_atomic(), irqs_disabled(),
current->pid, current->comm);
+ if (task_stack_end_corrupted(current))
+ printk(KERN_EMERG "Thread overran stack, or stack corrupted\n");
+
debug_show_held_locks(current);
if (irqs_disabled())
print_irqtrace_events(current);
^ permalink raw reply [flat|nested] 2+ messages in thread
* [tip:sched/core] sched/debug: Check for stack overflow in ___might_sleep()
2014-12-16 22:25 [PATCH] check for stack overflow in ___might_sleep Eric Sandeen
@ 2015-01-14 14:01 ` tip-bot for Eric Sandeen
0 siblings, 0 replies; 2+ messages in thread
From: tip-bot for Eric Sandeen @ 2015-01-14 14:01 UTC (permalink / raw)
To: linux-tip-commits
Cc: mingo, linux-kernel, tglx, torvalds, peterz, hpa, sandeen
Commit-ID: a8b686b3af4419f92e0ea5be1c76fb68363df8e6
Gitweb: http://git.kernel.org/tip/a8b686b3af4419f92e0ea5be1c76fb68363df8e6
Author: Eric Sandeen <sandeen@redhat.com>
AuthorDate: Tue, 16 Dec 2014 16:25:28 -0600
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Wed, 14 Jan 2015 13:34:14 +0100
sched/debug: Check for stack overflow in ___might_sleep()
Sometimes a "BUG: sleeping function called from invalid context"
message is not indicative of locking problems, but is the result
of a stack overflow corrupting the thread info.
Witness http://oss.sgi.com/archives/xfs/2014-02/msg00325.html
for example, which took a few go-rounds to sort out.
If we're printing the warning, things are wonky already, and
it'd be informative to check for the stack end corruption at this
point, too.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Link: http://lkml.kernel.org/r/5490B158.4060005@redhat.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
kernel/sched/core.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index c0accc0..56c9b79 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -7325,6 +7325,9 @@ void ___might_sleep(const char *file, int line, int preempt_offset)
in_atomic(), irqs_disabled(),
current->pid, current->comm);
+ if (task_stack_end_corrupted(current))
+ printk(KERN_EMERG "Thread overran stack, or stack corrupted\n");
+
debug_show_held_locks(current);
if (irqs_disabled())
print_irqtrace_events(current);
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-01-14 14:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-12-16 22:25 [PATCH] check for stack overflow in ___might_sleep Eric Sandeen
2015-01-14 14:01 ` [tip:sched/core] sched/debug: Check for stack overflow in ___might_sleep() tip-bot for Eric Sandeen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome