Date: Wed, 9 Jan 2008 08:03:51 -0800 (PST)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Roland McGrath <roland@redhat.com>
cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] show_task: real_parent
In-Reply-To: <20080109080323.8FCDC26F9A7@magilla.localdomain>
Message-ID: <alpine.LFD.1.00.0801090800360.3148@woody.linux-foundation.org>
References: <20080109080323.8FCDC26F9A7@magilla.localdomain>
User-Agent: Alpine 1.00 (LFD 882 2007-12-20)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1033
Lines: 26


On Wed, 9 Jan 2008, Roland McGrath wrote:
> 
> The show_task function invoked by sysrq-t et al displays the
> pid and parent's pid of each task.  It seems more useful to
> show the actual process hierarchy here than who is using
> ptrace on each process.

Hmm. It could go both ways. If the problem is some ptrace()/wait4() 
interaction issue (which is certainly not unheard of!) the parent that 
matters for the kernel may be the right thing to print out.

I wonder if we should just print out both (or perhaps print out the 
ptrace parent only if it differs from the normal parent?)

I'll apply this, because I agree that it's sensible in general, I just 
wonder how often anybody really even cares about the parent information 
when it's not about some wait-related issue..

		Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/