linux-kernel - Re: [PATCH v5 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info

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] [day] [month] [year] [list]

Message-ID: <20170120165407.GS6485@twins.programming.kicks-ass.net>
Date:   Fri, 20 Jan 2017 17:54:07 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Hari Bathini <hbathini@...ux.vnet.ibm.com>
Cc:     ast@...com, lkml <linux-kernel@...r.kernel.org>, acme@...nel.org,
        alexander.shishkin@...ux.intel.com, mingo@...hat.com,
        daniel@...earbox.net, rostedt@...dmis.org,
        Ananth N Mavinakayanahalli <ananth@...ux.vnet.ibm.com>,
        ebiederm@...ssion.com, sargun@...gun.me,
        Aravinda Prasad <aravinda@...ux.vnet.ibm.com>,
        brendan.d.gregg@...il.com, jolsa@...hat.com
Subject: Re: [PATCH v5 1/3] perf: add PERF_RECORD_NAMESPACES to include
 namespaces related info

On Fri, Jan 20, 2017 at 09:26:32PM +0530, Hari Bathini wrote:
> Hi Peter,
> 
> 
> On Wednesday 18 January 2017 07:56 PM, Peter Zijlstra wrote:
> >On Tue, Jan 17, 2017 at 07:47:22PM +0530, Hari Bathini wrote:
> >>With the advert of container technologies like docker, that depend
> >>on namespaces for isolation, there is a need for tracing support for
> >>namespaces. This patch introduces new PERF_RECORD_NAMESPACES event
> >>for tracing based on namespaces related info.
> >This fails to mention the whole namespace of namespaces issue Eric
> 
> IIUC, Eric wanted to have device info saved for each namespace separately
> to avoid the need for a namespace of namespaces in future.
> 
> >brought up. Where are we on that, and or why isn't it required?
> 
> 
> I did address that in v4 and haven't changed it in v5.
> I am not sure if it needs any mentioning in the changelog..

I would certainly have liked mention of the issue and its (non)
solution. It shows we thought about it and will help our older selves
remember.