From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Tejun Heo <tj@kernel.org>, Andrew Vagin <avagin@openvz.org>,
linux-kernel@vger.kernel.org, Roland McGrath <roland@redhat.com>,
Pavel Emelyanov <xemul@parallels.com>
Subject: Re: [PATCH] ptrace: add ability to get clear_tid_address
Date: Fri, 3 Feb 2012 20:54:04 +0400 [thread overview]
Message-ID: <20120203165404.GJ11834@moon> (raw)
In-Reply-To: <20120203164129.GA5341@redhat.com>
On Fri, Feb 03, 2012 at 05:41:29PM +0100, Oleg Nesterov wrote:
> On 02/03, Cyrill Gorcunov wrote:
> >
> > On Fri, Feb 03, 2012 at 08:25:19AM -0800, Tejun Heo wrote:
> >
> > > Ummm... this really doesn't fit in ptrace. Cyrill, why not put it
> > > together with other params you're exporting?
>
> I agree. And to me this looks strange: some info is exported via /proc,
> some things need ptrace.
>
> > We could add it to /proc/pid/stat (but I fear Andrew Morton shoot me then ;)
>
> may be you can add /proc/pid/misc_ugly^Wrandom_things_for_cr which
> you can extend as needed ;)
>
I personally don't mind to have /proc/pid/cr directory where we could
export all the data we might ever need. Still some things added (such
as /proc/pid/children) could be useful for other purposes as well, not
only c/r.
Cyrill
next prev parent reply other threads:[~2012-02-03 16:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 11:11 [PATCH] ptrace: add ability to get clear_tid_address Andrew Vagin
2012-02-03 16:25 ` Tejun Heo
2012-02-03 16:30 ` Cyrill Gorcunov
2012-02-03 16:41 ` Oleg Nesterov
2012-02-03 16:54 ` Cyrill Gorcunov [this message]
2012-02-03 16:45 ` Pavel Emelyanov
2012-02-03 16:51 ` Oleg Nesterov
2012-02-07 20:07 ` Pedro Alves
2012-02-07 20:56 ` Cyrill Gorcunov
2012-02-07 21:15 ` Pedro Alves
2012-02-07 21:51 ` Cyrill Gorcunov
2012-02-08 12:30 ` Pedro Alves
2012-02-08 12:42 ` Cyrill Gorcunov
2012-02-08 17:31 ` Oleg Nesterov
2012-02-08 18:04 ` Pedro Alves
2012-02-08 19:02 ` Oleg Nesterov
2012-02-08 19:20 ` Cyrill Gorcunov
2012-02-08 19:21 ` Jan Kratochvil
2012-02-08 19:42 ` Pedro Alves
2012-02-08 13:41 ` Andrew Vagin
2012-02-08 18:12 ` Jan Kratochvil
2012-02-10 3:02 ` Jamie Lokier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120203165404.GJ11834@moon \
--to=gorcunov@openvz.org \
--cc=avagin@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=roland@redhat.com \
--cc=tj@kernel.org \
--cc=xemul@parallels.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox