Commit-ID: 12b5c43486202dd4ff3cfd59a190984a0dd7f6fd Gitweb: http://git.kernel.org/tip/12b5c43486202dd4ff3cfd59a190984a0dd7f6fd Author: David Rientjes <rientjes@xxxxxxxxxx> AuthorDate: Mon, 4 May 2009 01:38:05 -0700 Committer: Ingo Molnar <mingo@xxxxxxx> CommitDate: Wed, 6 May 2009 12:09:30 +0200 sched: emit thread info flags with stack trace When a thread is oom killed and fails to exit, it's helpful to know which threads have access to memory reserves if the machine livelocks. This is done by testing for the TIF_MEMDIE thread info flag and should be displayed alongside stack traces to identify tasks that have access to such reserves but are still stuck allocating pages, for instance. It would probably be helpful in other cases as well, so all thread info flags are emitted when showing a task. [ Impact: extend debug printout info ] Signed-off-by: David Rientjes <rientjes@xxxxxxxxxx> Cc: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx> LKML-Reference: <alpine.DEB.2.00.0905040136390.15831@xxxxxxxxxxxxxxxxxxxxxxxxx> Signed-off-by: Ingo Molnar <mingo@xxxxxxx> --- kernel/sched.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/kernel/sched.c b/kernel/sched.c index 2a43a58..dfe2583 100644 --- a/kernel/sched.c +++ b/kernel/sched.c @@ -6610,8 +6610,9 @@ void sched_show_task(struct task_struct *p) #ifdef CONFIG_DEBUG_STACK_USAGE free = stack_not_used(p); #endif - printk(KERN_CONT "%5lu %5d %6d\n", free, - task_pid_nr(p), task_pid_nr(p->real_parent)); + printk(KERN_CONT "%5lu %5d %6d 0x%08x\n", free, + task_pid_nr(p), task_pid_nr(p->real_parent), + task_thread_info(p)->flags); show_stack(p, NULL); } -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|