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]
Date:   Tue, 11 Feb 2020 10:06:35 +0000
From:   Marek Majkowski <marek@...udflare.com>
To:     Jiri Olsa <jolsa@...hat.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

Jirka,

On Tue, Feb 4, 2020 at 7:27 PM Jiri Olsa <jolsa@...hat.com> wrote:
> > 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
>
> hi,
> could you guys please share more details on what you run exactly,
> and perhaps that change you mentioned?

I was debugging gvisor (runsc), which does execve(/proc/self/exe), and
then messes up with its mount namespace. The effect is that the binary
running doesn't exist in the mount namespace. This confuses perf,
which fails to load symbols for that process.

To my understanding, by default, perf looks for the binary in the
process mount namespace. In this case clearly the binary wasn't there.
Ivan wrote a rough patch [1], which I just confirmed works. The patch
attempts, after a failure to load binary from pids mount namespace, to
load binary from the default mount namespace (the one running perf).

[1] https://lkml.org/lkml/2019/12/5/878

Marek

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ