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
| ||
|
Date: Mon, 12 Jul 2010 10:58:01 +0900 (JST) From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> To: Christoph Hellwig <hch@...radead.org> Cc: kosaki.motohiro@...fujitsu.com, Eric B Munson <emunson@...bm.net>, akpm@...ux-foundation.org, mingo@...hat.com, hugh.dickins@...cali.co.uk, riel@...hat.com, peterz@...radead.org, anton@...ba.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: [PATCH 1/2] Add trace events to mmap and brk > Hmm, thinking about it a bit more, what do you trace events give us that > the event based syscall tracer doesn't? Yup. I think we need two tracepoint. 1) need to know userland argument. -> syscall tracer 2) need to know actual vma change. -> need to trace more low layer As I said, if userland app have following code, mmap(0x10000, PROT_READ|PROT_WRITE) mmap(0x10000, PROT_NONE) second mmap implicitly unmap firt mmap region and map another region. so if we want to track munmap activity, syscall exiting point is not so good place. we need to trace per-vma activity. btw, perf_event_mmap() already take vma argument. -- 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/
Powered by blists - more mailing lists