linux-kernel - Re: [PATCH 0/3] Handle chroot tasks properly (v1)

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: <2db9fab4-0aff-b8b0-5012-13556ea496af@linux.intel.com>
Date:   Mon, 31 Jan 2022 17:16:14 -0800
From:   Andi Kleen <ak@...ux.intel.com>
To:     Namhyung Kim <namhyung@...nel.org>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Jiri Olsa <jolsa@...hat.com>
Cc:     Ingo Molnar <mingo@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Ian Rogers <irogers@...gle.com>
Subject: Re: [PATCH 0/3] Handle chroot tasks properly (v1)

On 1/28/2022 12:39 PM, Namhyung Kim wrote:
> Hello,
>
> I found that perf tools don't work well with tasks in a chroot.  The
> filenames in MMAP record are from the root directory of the task so
> it's different than what it sees from outside.

While that's a real problem, and for chroot it can be fixed, it's much 
more complicated for the more complex container namespace case with 
custom mounts, including loop back, etc.

It seems it really need some kind of agent to handle all cases. For 
example the agent could understand container metadata formats and then 
do the right thing.

-Andi