linux-kernel - Re: [RFC PATCH 01/17] perf: Allow mmapping only user page

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: <20170913125825.dmh2f5qwobd6e2sn@pd.tnic>
Date:   Wed, 13 Sep 2017 14:58:25 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Cc:     Peter Zijlstra <a.p.zijlstra@...llo.nl>,
        Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
        acme@...hat.com, kirill.shutemov@...ux.intel.com, rric@...nel.org
Subject: Re: [RFC PATCH 01/17] perf: Allow mmapping only user page

On Wed, Sep 13, 2017 at 02:35:42PM +0300, Alexander Shishkin wrote:
> Well, it is a 'defined' interface: there's the 'struct
> perf_event_mmap_page' with versioning and whatnot, which is used for all
> the ring buffer metainformation. Or am I misunderstanding your question?

No, you're not. Looking at perf_event_mmap_page, sounds like my concerns are
addressed. :)

Thx.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.