linux-kernel - Re: perf not picking up symbols for namespaced processes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200204192657.GB1554679@krava>
Date:   Tue, 4 Feb 2020 20:26:57 +0100
From:   Jiri Olsa <jolsa@...hat.com>
To:     Marek Majkowski <marek@...udflare.com>
Cc:     Ivan Babrou <ivan@...udflare.com>,
        kernel-team <kernel-team@...udflare.com>,
        Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Namhyung Kim <namhyung@...nel.org>, sashal@...nel.org,
        Kenton Varda <kenton@...udflare.com>
Subject: Re: perf not picking up symbols for namespaced processes

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@...udflare.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