From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758300AbZEGHl1 (ORCPT ); Thu, 7 May 2009 03:41:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757055AbZEGHlF (ORCPT ); Thu, 7 May 2009 03:41:05 -0400 Received: from hera.kernel.org ([140.211.167.34]:50632 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756323AbZEGHlD (ORCPT ); Thu, 7 May 2009 03:41:03 -0400 Date: Thu, 7 May 2009 07:39:44 GMT From: tip-bot for David Rientjes To: linux-tip-commits@vger.kernel.org Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com, a.p.zijlstra@chello.nl, sfr@canb.auug.org.au, tglx@linutronix.de, rientjes@google.com, mingo@elte.hu Reply-To: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl, tglx@linutronix.de, sfr@canb.auug.org.au, rientjes@google.com, mingo@elte.hu In-Reply-To: References: Subject: [tip:sched/core] sched: emit thread info flags with stack trace Message-ID: Git-Commit-ID: aa47b7e0f89b9998dad4d1667447e8cb7703ff4e X-Mailer: tip-git-log-daemon MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (hera.kernel.org [127.0.0.1]); Thu, 07 May 2009 07:39:47 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit-ID: aa47b7e0f89b9998dad4d1667447e8cb7703ff4e Gitweb: http://git.kernel.org/tip/aa47b7e0f89b9998dad4d1667447e8cb7703ff4e Author: David Rientjes AuthorDate: Mon, 4 May 2009 01:38:05 -0700 Committer: Ingo Molnar CommitDate: Thu, 7 May 2009 09:36:28 +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. ( v2: fix warning reported by Stephen Rothwell ) [ Impact: extend debug printout info ] Signed-off-by: David Rientjes Cc: Peter Zijlstra Cc: Stephen Rothwell LKML-Reference: Signed-off-by: Ingo Molnar --- kernel/sched.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/kernel/sched.c b/kernel/sched.c index 2a43a58..5aa63f5 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%08lx\n", free, + task_pid_nr(p), task_pid_nr(p->real_parent), + (unsigned long)task_thread_info(p)->flags); show_stack(p, NULL); }