linux-kernel - Re: [RFC PATCH 1/6] perf: Move mlock accounting to ring buffer allocation

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: <20160923152737.GN5008@twins.programming.kicks-ass.net>
Date:   Fri, 23 Sep 2016 17:27:37 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Cc:     Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
        vince@...ter.net, eranian@...gle.com,
        Arnaldo Carvalho de Melo <acme@...radead.org>,
        tglx@...utronix.de, ak@...ux.intel.com
Subject: Re: [RFC PATCH 1/6] perf: Move mlock accounting to ring buffer
 allocation

On Fri, Sep 23, 2016 at 05:27:22PM +0300, Alexander Shishkin wrote:
> > Afaict there's no actual need to hide the AUX buffer for this sampling
> > stuff; the user knows about all this and can simply mmap() the AUX part.
> 
> Yes, you're right here. We could also re-use the AUX record, adding a
> new flag for this. It may be even better if I can work out the
> inheritance (the current code doesn't handle inheritance at the moment
> in case we decide to scrap it).

What is the exact problem with inheritance? You can inherit PT (and
other) events just fine, and their output redirects to the original
(AUX) buffer too.

Is the problem untangling which part of the AUX buffer belongs to which
task upon sample?