linux-kernel - Re: [PATCH] Add trace event for munmap

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100708175147.GA17525@infradead.org>
Date:	Thu, 8 Jul 2010 13:51:48 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Eric B Munson <ebmunson@...ibm.com>,
	Eric B Munson <emunson@...bm.net>, akpm@...ux-foundation.org,
	mingo@...hat.com, hugh.dickins@...cali.co.uk, riel@...hat.com,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org, anton@...ba.org
Subject: Re: [PATCH] Add trace event for munmap

On Thu, Jul 08, 2010 at 07:48:08PM +0200, Peter Zijlstra wrote:
> On Thu, 2010-07-08 at 13:35 -0400, Christoph Hellwig wrote:
> 
> > What kind of infrastructure is perf using for recording
> > mmap()/mremap()/brk() information?
> 
> A direct hook into mmap_region(), see perf_event_mmap().
> 
> We used to only track VM_EXEC regions, but these days we can also track
> data regions (although it wouldn't track mremap and brk I think).
> 
> We need the VM_EXEC maps to make sense of the instruction pointer
> samples.
> 
> Eric recently added support for !VM_EXEC mmap() in order to interpret
> linear addresses provided by things like the software pagefault events
> and certain powerpc hardware events.

Maybe the user reporting should use trace points everywhere, leaving
the direct hook just for the executable tracking?

--
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/