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: Sun, 03 Aug 2008 08:19:28 -0400 From: fche@...hat.com (Frank Ch. Eigler) To: "Ming Lei" <tom.leiming@...il.com> Cc: "Steven Rostedt" <rostedt@...dmis.org>, linux-kernel@...r.kernel.org, "Ingo Molnar" <mingo@...e.hu>, "Andrew Morton" <akpm@...ux-foundation.org>, "Steven Rostedt" <srostedt@...hat.com> Subject: Re: [RFC] ftrace: support tracing functions in one module "Ming Lei" <tom.leiming@...il.com> writes: > [...] For example, one may only have interest in functions calling > in usbcore.ko, but he must trace all the functions calling in the > kernel, so the tracing result is too large to use it. [...] Until ftrace gains this ability, you could use systemtap: # cat callret.stp probe $1.call { printf ("%s <- %s\n", thread_indent(1), probefunc()) } probe $1.return { printf ("%s -> %s\n", thread_indent(-1), probefunc()) } # stap callret.stp 'module("usbcore").function("*")' [...] ^C # (One can also add conditions based on function parameters, processes, whatever; soon it'll be easy to trace all function parameters.) - FChE -- 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