linux-kernel - [PATCH 0/2] tracing: userspace stacktraces

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]

Message-Id: <1227353328-16104-1-git-send-email-edwintorok@gmail.com>
Date:	Sat, 22 Nov 2008 13:28:46 +0200
From:	Török Edwin <edwintorok@...il.com>
To:	mingo@...e.hu
Cc:	srostedt@...hat.com, a.p.zijlstra@...llo.nl, sandmann@...mi.au.dk,
	linux-kernel@...r.kernel.org, viro@...IV.linux.org.uk,
	Török Edwin <edwintorok@...il.com>
Subject: [PATCH 0/2] tracing: userspace stacktraces

Hi,

I am resending my patches, differrences from previous send:
* fixed some style issues
* introduce seq_print_user_ip helper
* make mangle_path global and document
* use mangle_path instead of abusing seq_file in trace_seq_path
* fix subject line and commit messages

These patches apply on top of tip/master,
commit 50598e26c1360d4c0edcabc50035d084ee8d3d70

Török Edwin (2):
  tracing: add support for userspace stacktraces in tracing/iter_ctrl
  tracing: identify which executable object the userspace address
    belongs to

 Documentation/ftrace.txt     |   16 ++++-
 arch/x86/kernel/stacktrace.c |   57 +++++++++++++++
 fs/seq_file.c                |   14 ++++-
 include/linux/seq_file.h     |    1 +
 include/linux/stacktrace.h   |    8 ++
 kernel/trace/trace.c         |  165 ++++++++++++++++++++++++++++++++++++++++++
 kernel/trace/trace.h         |   10 +++
 7 files changed, 269 insertions(+), 2 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/