linux-kernel - Re: perf MMAP2 interface and COW faults

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: <20140314132447.GW27965@twins.programming.kicks-ass.net>
Date:	Fri, 14 Mar 2014 14:24:47 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Don Zickus <dzickus@...hat.com>
Cc:	eranian@...gle.com, jmario@...hat.com, jolsa@...hat.com,
	acme@...hat.com, linux-kernel@...r.kernel.org, lwoodman@...hat.com
Subject: Re: perf MMAP2 interface and COW faults

On Fri, Mar 14, 2014 at 08:58:37AM -0400, Don Zickus wrote:
> Hmmm.  That will probably work for future mmap events.  My problem is for
> synthesized mmap events.  We read the same protection bits from
> /proc/<pid>/maps file, so I assume the same strategy can work for those
> events too?

Yeah, so /proc/$pid/maps doesn't contain all those bits, but it does
have the prot read/write/exec and flags shared/private thing, which
should be sufficient for your needs.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/