public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/3] [GIT PULL] tracing: three more updates
Date: Wed, 04 Dec 2019 21:04:59 -0500	[thread overview]
Message-ID: <20191205020459.023316620@goodmis.org> (raw)


Linus,

Two fixes and one patch that was missed:

 Fixes:

  - Missing __print_hex_dump undef for processing new function in trace events
  - Stop WARN_ON messages when lockdown disables tracing on boot up

 Enhancement:

  - Debug option to inject trace events from userspace (for rasdaemon)

The enhancement has its own config option and is non invasive. It's been
discussed for sever months and should have been added to my original
push, but I never pulled it into my queue.

Please pull the latest trace-v5.5-2 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v5.5-2

Tag SHA1: 075c954bfa42bcd2dad254f1fe6fcd81197512de
Head SHA1: a356646a56857c2e5ad875beec734d7145ecd49a


Cong Wang (1):
      tracing: Introduce trace event injection

Piotr Maziarz (1):
      tracing: Fix __print_hex_dump scope

Steven Rostedt (VMware) (1):
      tracing: Do not create directories if lockdown is in affect

----
 include/trace/trace_events.h       |   1 +
 kernel/trace/Kconfig               |   9 +
 kernel/trace/Makefile              |   1 +
 kernel/trace/ring_buffer.c         |   6 +
 kernel/trace/trace.c               |  17 ++
 kernel/trace/trace.h               |   1 +
 kernel/trace/trace_events.c        |   6 +
 kernel/trace/trace_events_inject.c | 331 +++++++++++++++++++++++++++++++++++++
 8 files changed, 372 insertions(+)
 create mode 100644 kernel/trace/trace_events_inject.c

             reply	other threads:[~2019-12-05  2:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05  2:04 Steven Rostedt [this message]
2019-12-05  2:05 ` [PATCH 1/3] tracing: Fix __print_hex_dump scope Steven Rostedt
2019-12-05  2:05 ` [PATCH 2/3] tracing: Introduce trace event injection Steven Rostedt
2019-12-05  2:05 ` [PATCH 3/3] tracing: Do not create directories if lockdown is in affect Steven Rostedt
2020-01-10 16:31   ` Steven Rostedt
2020-01-10 16:54     ` Greg KH
2020-01-10 17:02       ` Steven Rostedt
  -- strict thread matches above, loose matches on Subject: below --
2016-05-22 20:28 [PATCH 0/3] [GIT PULL] tracing: Three more updates Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191205020459.023316620@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox