[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120125152958.GA7888@moon>
Date: Wed, 25 Jan 2012 19:29:58 +0400
From: Cyrill Gorcunov <gorcunov@...il.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@...il.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Pavel Emelyanov <xemul@...allels.com>,
Serge Hallyn <serge.hallyn@...onical.com>,
Kees Cook <keescook@...omium.org>, Tejun Heo <tj@...nel.org>,
Andrew Vagin <avagin@...nvz.org>,
Alexey Dobriyan <adobriyan@...il.com>
Subject: Re: [patch 1/4] fs, proc: Introduce /proc/<pid>/task/<tid>/children
entry v8
On Wed, Jan 25, 2012 at 10:55:51AM +0400, Cyrill Gorcunov wrote:
> >
> > Now that you have reminded me of this thread. I can say that the
> > link would need to look like ../../pid. Our children will always
> > be thread group leaders, so we can safely point to the /proc/<pid>
> > directories. So readlink would return ../../<pid> or however many
> > dots are needed. Follow link could just warp us to that directory
> > as it does for the other magic proc symlinks.
> >
> > My feeling is that a children subdirectory would be a lot more useful
> > than a simple file that lists the children.
> >
>
> I'll check what I can do, thanks.
>
Sigh. This will require complete code rewrite. And since I've just
made it to live under CONFIG_CHECKPOINT_RESTORE I would prefer if
we stick with children file. So if there are no strong objections
agains 'children' as a file, could we leave it as is, ie in
stream-of-pids form?
Cyrill
--
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/
Powered by blists - more mailing lists