linux-kernel - Re: [PATCH] show_task: real

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 9 Jan 2008 08:03:51 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Roland McGrath <roland@...hat.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] show_task: real_parent

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/