From: tip-bot for David Rientjes <rientjes@google.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
a.p.zijlstra@chello.nl, tglx@linutronix.de, rientjes@google.com,
mingo@elte.hu
Subject: [tip:sched/core] sched: emit thread info flags with stack trace
Date: Wed, 6 May 2009 10:25:44 GMT [thread overview]
Message-ID: <tip-12b5c43486202dd4ff3cfd59a190984a0dd7f6fd@git.kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.00.0905040136390.15831@chino.kir.corp.google.com>
Commit-ID: 12b5c43486202dd4ff3cfd59a190984a0dd7f6fd
Gitweb: http://git.kernel.org/tip/12b5c43486202dd4ff3cfd59a190984a0dd7f6fd
Author: David Rientjes <rientjes@google.com>
AuthorDate: Mon, 4 May 2009 01:38:05 -0700
Committer: Ingo Molnar <mingo@elte.hu>
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@google.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
LKML-Reference: <alpine.DEB.2.00.0905040136390.15831@chino.kir.corp.google.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
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);
}
next prev parent reply other threads:[~2009-05-06 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 8:38 [patch] sched: emit thread info flags with stack trace David Rientjes
2009-05-06 10:12 ` Ingo Molnar
2009-05-06 10:25 ` tip-bot for David Rientjes [this message]
2009-05-07 7:39 ` [tip:sched/core] " tip-bot for David Rientjes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tip-12b5c43486202dd4ff3cfd59a190984a0dd7f6fd@git.kernel.org \
--to=rientjes@google.com \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox