linux-kernel - [for-next][PATCH 0/7] tracing: Updates for 4.5 (and some stuff going into 4.4)

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: <20151125160838.739491216@goodmis.org>
Date:	Wed, 25 Nov 2015 11:08:38 -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/7] tracing: Updates for 4.5 (and some stuff going into 4.4)

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

Head SHA1: ffaea3b8472da0f0e5a2b4fc9ccefb1ff460e824


Steven Rostedt (Red Hat) (6):
      ring-buffer: Update read stamp with first real commit on page
      ring-buffer: Put back the length if crossed page with add_timestamp
      ftracetest: Add instance create and delete test
      ring-buffer: Use READ_ONCE() for most tail_page access
      ring-buffer: Remove redundant update of page timestamp
      ring-buffer: Process commits whenever moving to a new page.

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

----
 kernel/module.c                                    | 18 ++++-
 kernel/trace/ring_buffer.c                         | 74 +++++++++---------
 kernel/trace/trace_events_trigger.c                | 10 ++-
 .../selftests/ftrace/test.d/instances/instance.tc  | 90 ++++++++++++++++++++++
 4 files changed, 147 insertions(+), 45 deletions(-)
 create mode 100644 tools/testing/selftests/ftrace/test.d/instances/instance.tc
--
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/