mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Marek Majkowski <marek@cloudflare.com>
Cc: Ivan Babrou <ivan@cloudflare.com>,
	kernel-team <kernel-team@cloudflare.com>,
	Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	sashal@kernel.org, Kenton Varda <kenton@cloudflare.com>
Subject: Re: perf not picking up symbols for namespaced processes
Date: Tue, 4 Feb 2020 20:26:57 +0100	[thread overview]
Message-ID: <20200204192657.GB1554679@krava> (raw)
In-Reply-To: <CAJPywTKC8=O0zmNm-W4OUENpoZfrbr1Ts38gQw2ZA608_u5wpw@mail.gmail.com>

On Tue, Feb 04, 2020 at 03:09:48PM +0000, Marek Majkowski wrote:
> On Fri, Dec 6, 2019 at 2:17 AM Ivan Babrou <ivan@cloudflare.com> wrote:
> >
> > I'm not very good at this, but the following works for me. If you this
> > is in general vicinity of what you expected, I can email patch
> > properly.
> >
> 
> Thanks for the patch, I can confirm it works. I had this problem today
> when playing
> with gvisor. Gvisor is starting up in a fresh mount namespace and perf fails
> to read the symbols. Stracing perf shows:
> 
> 11913 openat(AT_FDCWD, "/proc/9512/ns/mnt", O_RDONLY) = 197
> 11913 setns(197, CLONE_NEWNS) = 0
> 11913 stat("/home/marek/bin/runsc-debug", 0x7fffffff8480) = -1 ENOENT
> (No such file or directory)
> 11913 setns(196, CLONE_NEWNS) = 0
> 
> Which of course makes no sense - the runsc-debug binary does not exist in the
> empty mount namespace of the restricted runsc process.

hi,
could you guys please share more details on what you run exactly,
and perhaps that change you mentioned?

thanks,
jirka


  reply	other threads:[~2020-02-04 19:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05  3:46 Ivan Babrou
2019-12-05 12:33 ` Arnaldo Carvalho de Melo
2019-12-06  2:17   ` Ivan Babrou
2020-02-04 15:09     ` Marek Majkowski
2020-02-04 19:26       ` Jiri Olsa [this message]
2020-02-11 10:06         ` Marek Majkowski
2020-02-11 13:46           ` Arnaldo Carvalho de Melo
2020-02-11 13:54             ` Marek Majkowski
2020-02-11 14:28               ` 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=20200204192657.GB1554679@krava \
    --to=jolsa@redhat.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=ivan@cloudflare.com \
    --cc=kenton@cloudflare.com \
    --cc=kernel-team@cloudflare.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek@cloudflare.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sashal@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

all inboxes | Powered by JetHome®