[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87h9b01ja2.fsf@x220.int.ebiederm.org>
Date: Thu, 04 Aug 2016 13:27:49 -0500
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Aravinda Prasad <aravinda@...ux.vnet.ibm.com>
Cc: Hari Bathini <hbathini@...ux.vnet.ibm.com>, daniel@...earbox.net,
peterz@...radead.org, linux-kernel@...r.kernel.org,
acme@...nel.org, alexander.shishkin@...ux.intel.com,
mingo@...hat.com, paulus@...ba.org, kernel@...p.com,
rostedt@...dmis.org, viro@...iv.linux.org.uk, ananth@...ibm.com,
Linux Containers <containers@...ts.linux-foundation.org>
Subject: Re: [RFC PATCH v2 0/3] perf/tracefs: Container-aware tracing support
Aravinda Prasad <aravinda@...ux.vnet.ibm.com> writes:
> On Thursday 04 August 2016 08:29 AM, Eric W. Biederman wrote:
>> Hari Bathini <hbathini@...ux.vnet.ibm.com> writes:
>>
>>> This RFC patch set supports filtering container specific events
>>> when perf tool is executed inside a container. The patches apply
>>> cleanly on v4.7.0-rc7
>>>
>>> Changes from v1:
>>> 1/3. Revived earlier approach[1] with cgroup namespace instead
>>> of pid namespace
>>> 2/3. New patch that adds instance support for uprobe events in
>>> tracefs filesystem
>>> 3/3. New patch that adds "newinstance" mount option for tracefs
>>> filesystem
>> "newinstace" ick no.
>>
>> I see no justification anywhere why the perf cgroup is not enough for
>> this.
>
> perf cgroup is not enough for uprobes, because even with perf cgroups a
> user within a container can still list/delete uprobes registered in
> other containers.
Just to be clear, even if there is one cgroup per container?
Eric
Powered by blists - more mailing lists