linux-kernel - [PATCH tip 0/2] utrace-ftrace engine v3

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sun,  5 Apr 2009 10:17:52 -0400
From:	"Frank Ch. Eigler" <fche@...stic.org>
To:	linux-kernel@...r.kernel.org, utrace-devel@...hat.com
Cc:	systemtap@...rces.redhat.com, fweisbec@...il.com,
	rostedt@...dmis.org, mingo@...e.hu,
	"Frank Ch. Eigler" <fche@...stic.org>
Subject: [PATCH tip 0/2] utrace-ftrace engine v3

This version of the utrace-ftrace engine represents bringing v2 (as
posted along with utrace two weeks ago) up to parity with the
tip/tracing/syscalls one in terms of using the system call
pretty-printing tables.  This patch applies to the
tip/tracing/syscalls tree, except that it assumes that utrace patches
are also applied beforehand.

Next up could be adding an option to use the filterable TRACE_EVENT
tracepoint engine instead of (or in addition to?)  the hand-written
trace record management & formatting.

Next up could also be removal of the syscall-tracing prototype, if
people are so inclined.

Frank Ch. Eigler (2):
  make arch_init_ftrace_syscalls multiply callable
  utrace-based ftrace "process" engine, v3

 arch/x86/kernel/ftrace.c     |    3 +
 include/linux/processtrace.h |   51 ++++
 kernel/trace/Kconfig         |    8 +
 kernel/trace/Makefile        |    1 +
 kernel/trace/trace.h         |    9 +
 kernel/trace/trace_process.c |  642 ++++++++++++++++++++++++++++++++++++++++++
 6 files changed, 714 insertions(+), 0 deletions(-)
 create mode 100644 include/linux/processtrace.h
 create mode 100644 kernel/trace/trace_process.c

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