| 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
| ||
|
Message-Id: <1252923251-6735-1-git-send-email-jolsa@redhat.com> Date: Mon, 14 Sep 2009 12:14:09 +0200 From: jolsa@...hat.com To: mingo@...e.hu, rostedt@...dmis.org Cc: linux-kernel@...r.kernel.org Subject: [RFC PATCH 0/2] tracing - signal tracer, support multiple pids in set_pid_ftrace I was debugging some ptrace applications and got to the idea of tracing signals - signal tracer. There's probably possibility to trace more info than just signal delivery info (like ignored signals deliveries, queue status...). While doing this I realized it might be worth to have ability to trace more independent processes via set_pid_ftrace file. Althought I'm sending this as RFC, attached patches work for me. I'm open to any suggestions/comments/ideas. 1/2 - signal trace 2/2 - multiple pids support for set_pid_ftrace file thanks, jirka Signed-off-by: Jiri Olsa <jolsa@...hat.com> --- include/linux/signaltrace.h | 22 ++++ include/linux/tracehook.h | 14 +++ kernel/signal.c | 3 + kernel/trace/Kconfig | 11 ++ kernel/trace/Makefile | 1 + kernel/trace/ftrace.c | 226 +++++++++++++++++++++++++++++++------------ kernel/trace/trace.h | 13 ++- kernel/trace/trace_signal.c | 132 +++++++++++++++++++++++++ 8 files changed, 356 insertions(+), 66 deletions(-) -- 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