linux-kernel - [for-next][PATCH 0/5] tracing: More updates for 3.13

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: <20131107040002.605895766@goodmis.org>
Date:	Wed, 06 Nov 2013 23:00:02 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...nel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [for-next][PATCH 0/5] tracing: More updates for 3.13

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

Head SHA1: 20b72e76c42bc4f0dd091f9faee542ea45ad6b5e


Cody P Schafer (1):
      tracing: Open tracer when ftrace_dump_on_oops is used

Geyslan G. Bem (2):
      tracing: Add helper function tracing_is_disabled()
      tracing: Do not assign filp->private_data to freed memory

Steven Rostedt (1):
      Merge branch 'trace/ftrace/core' into trace/for-next

Steven Rostedt (Red Hat) (2):
      tracing: Remove unused function ftrace_off_permanent()
      tracing: Do not use signed enums with unsigned long long in fgragh output

----
 include/linux/kernel.h               |  2 --
 kernel/trace/trace.c                 | 31 ++++++++++++++++---------------
 kernel/trace/trace.h                 |  3 +++
 kernel/trace/trace_events.c          |  9 ++++++++-
 kernel/trace/trace_functions_graph.c | 22 +++++++++++-----------
 5 files changed, 38 insertions(+), 29 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/