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: Wed, 21 Jul 2010 22:34:12 +0900 (JST) From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> To: Eric B Munson <emunson@...bm.net> Cc: kosaki.motohiro@...fujitsu.com, akpm@...ux-foundation.org, mingo@...hat.com, hugh.dickins@...cali.co.uk, riel@...hat.com, peterz@...radead.org, anton@...ba.org, hch@...radead.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: [PATCH 1/2] Add trace points to mmap, munmap, and brk > This patch adds trace points to mmap, munmap, and brk that will report > relevant addresses and sizes before each function exits successfully. > > Signed-off-by: Eric B Munson <emunson@...bm.net> I don't think this is good idea. if you need syscall result, you should use syscall tracer. IOW, This tracepoint bring zero information. Please see perf_event_mmap() usage. Our kernel manage adress space by vm_area_struct. we need to trace it if we need to know what kernel does. Thanks. -- 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