From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/6525] need utrace task-finder-based pid->execname, pid->cwd-path-name tables
Date: Mon, 04 Aug 2014 15:10:00 -0000 [thread overview]
Message-ID: <bug-6525-6586-rpv3f7LmOU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-6525-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=6525
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
CC| |dsmith at redhat dot com
Resolution|--- |FIXED
--- Comment #11 from David Smith <dsmith at redhat dot com> ---
(In reply to Martin Cermak from comment #10)
> Right now stap can access parts of the procfs. How about declassifying
> certain userspace information right from there? That might bring systemtap
> closer to the sysadmins.
Unless I'm forgetting something, systemtap can't really access procfs. We can
add additional information to procfs (via procfs probes), but we really can't
access other parts of procfs. If procfs was a real filesystem, we might be able
to traverse it inside a systemtap module, but even then once we found the right
file we wouldn't be able to open it and read it.
Until we can think of a good way to accomplish this, I'm going to reclose this
one.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-08-04 15:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-6525-6586@http.sourceware.org/bugzilla/>
2013-05-24 21:29 ` fche at redhat dot com
2014-07-31 8:52 ` mcermak at redhat dot com
2014-08-04 13:48 ` mcermak at redhat dot com
2014-08-04 15:10 ` dsmith at redhat dot com [this message]
2014-08-04 16:07 ` fche at redhat dot com
2014-08-04 16:20 ` dsmith at redhat dot com
2014-08-04 16:45 ` fche at redhat dot com
2014-08-04 17:16 ` dsmith at redhat dot com
2014-08-04 17:26 ` fche at redhat dot com
2014-10-23 0:58 ` thepouar at gmail dot com
2014-10-23 0:58 ` thepouar at gmail dot com
2014-10-23 1:01 ` thepouar at gmail dot com
2014-10-23 1:02 ` thepouar at gmail dot com
2015-10-08 14:54 ` dsmith at redhat dot com
2015-10-12 16:20 ` dsmith at redhat dot com
2008-05-16 16:02 [Bug tapsets/6525] New: " fche at redhat dot com
2009-01-16 2:33 ` [Bug tapsets/6525] " fche at redhat dot com
2009-02-26 9:17 ` wenji dot huang at oracle dot com
2009-02-26 9:35 ` fche at redhat dot com
2009-02-27 1:31 ` wenji dot huang at oracle dot com
2009-02-27 1:59 ` wenji dot huang at oracle dot com
2009-03-02 21:46 ` dsmith at redhat dot com
2009-03-03 13:22 ` wenji dot huang at oracle dot com
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=bug-6525-6586-rpv3f7LmOU@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).