linux-kernel - Re: [PATCH] proc: Expose /proc/<pid>/task/<tid>/children unconditionally

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]

Message-ID: <20130626072102.GE1726@moon>
Date:	Wed, 26 Jun 2013 11:21:02 +0400
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	Oleg Nesterov <oleg@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] proc: Expose /proc/<pid>/task/<tid>/children
 unconditionally

On Tue, Jun 25, 2013 at 03:01:35PM -0700, Andy Lutomirski wrote:
> 
> This is a little strange.  It looks like ppid (in status) shows the
> tgid, but the actual real_parent can refer to a thread (as opposed to
> a thread group leader), and task/tid/children respects that.  So the
> tree that you get by following task/tid/ children won't be quite the
> same as the tree you get by following ppid.
> 
> I wonder if the ptid should be added to status.  Is there anything
> (other than task/tid/children) that cased which thread is the parent
> of a given task?

None I know of. As to ptid -- sounds reasonable to me. Oleg?
--
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/