From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: "David S. Ahern" <daahern@cisco.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] perf tools: Add symfs option for off-box analysis using specified tree
Date: Tue, 14 Dec 2010 12:39:29 -0200 [thread overview]
Message-ID: <20101214143929.GE13425@ghostprotocols.net> (raw)
In-Reply-To: <4D078037.9060207@cisco.com>
Em Tue, Dec 14, 2010 at 07:33:27AM -0700, David S. Ahern escreveu:
> On 12/14/10 07:06, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Dec 14, 2010 at 10:52:45AM -0200, Arnaldo Carvalho de Melo escreveu:
> >> Ok, there are still some problems:
> >> It is escaping the symfs jail for /home/acme/bin/perf, /lib64/libpthread-2.5.so
> >> and kernel modules, investigating...
> > Those 'G' signals means DSO__ORIG_GUEST_KMODULE, since you were not
> > prefixing that case with symfs, it was the jail leak point, fixed, doing
> > some more testing before merging.
> yuk. I did not touch the hypervisor paths.
> So the 'guest' route is tried all the time because of the origin list --
> even when it's not applicable.
Right, I don't like the way kvm is supported, will revisit this at some
point.
If build-ids were first class citizens, all this would be moot :-\
- Arnaldo
next prev parent reply other threads:[~2010-12-14 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 20:27 [PATCH v3] perf tools: Add symfs option for off-box analysis using specified tree David Ahern
2010-12-14 12:24 ` Arnaldo Carvalho de Melo
2010-12-14 12:52 ` Arnaldo Carvalho de Melo
2010-12-14 14:06 ` Arnaldo Carvalho de Melo
2010-12-14 14:33 ` David S. Ahern
2010-12-14 14:39 ` Arnaldo Carvalho de Melo [this message]
2010-12-14 14:27 ` David S. Ahern
2010-12-14 14:35 ` Arnaldo Carvalho de Melo
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=20101214143929.GE13425@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=daahern@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.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 NNTP newsgroup(s).