linux-kernel - [for-next][PATCH 0/5] tracing: Better output when ftrace

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:	Wed, 25 Nov 2015 21:19:03 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [for-next][PATCH 0/5] tracing: Better output when ftrace_bug() is hit

Better output in ftrace_bug() for debugging when ftrace fails to modify
a location. Also, removed module modifications that were left over from
debugging before (rebased).

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next

Head SHA1: 39daa7b9e89512f234b7fb5d55812a78318251fc


Steven Rostedt (Red Hat) (4):
      ring-buffer: Process commits whenever moving to a new page.
      ftrace: Add new type to distinguish what kind of ftrace_bug()
      ftrace: Add variable ftrace_expected for archs to show expected code
      ftrace: Show all tramps registered to a record on ftrace_bug()

Tom Zanussi (1):
      tracing: Update cond flag when enabling or disabling a trigger

----
 arch/x86/kernel/ftrace.c            |  9 ++++
 include/linux/ftrace.h              | 15 ++++++
 kernel/trace/ftrace.c               | 92 ++++++++++++++++++++++++++++++++-----
 kernel/trace/ring_buffer.c          |  7 +++
 kernel/trace/trace_events_trigger.c | 10 ++--
 5 files changed, 117 insertions(+), 16 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/