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/2] [GIT PULL] tracing: Some minor fixes
Date: Tue, 05 Jan 2016 12:17:15 -0500	[thread overview]
Message-ID: <20160105171715.485344115@goodmis.org> (raw)


Linus,

Two more fixes.

 1. The recordmcount change had an output that used sprintf() (incorrectly)
    when it should have been a fprintf() to stderr.

 2. The printk_formats file could crash if someone added a trace_printk()
    in the core kernel, and also added one in a module. This does not
    affect production kernels. Only kernels where developers add trace_printk()
    for debugging can crash.

Please pull the latest trace-v4.4-rc4-3 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.4-rc4-3

Tag SHA1: 88d7ab59dbb2c2dd97158589e7c3b1b44cd792be
Head SHA1: f36d1be2930ede0a1947686e1126ffda5d5ee1bb


Colin Ian King (1):
      ftrace/scripts: Fix incorrect use of sprintf in recordmcount

Qiu Peiyang (1):
      tracing: Fix setting of start_index in find_next()

----
 kernel/trace/trace_printk.c | 1 +
 scripts/recordmcount.c      | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

             reply	other threads:[~2016-01-05 17:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 17:17 Steven Rostedt [this message]
2016-01-05 17:17 ` [PATCH 1/2] ftrace/scripts: Fix incorrect use of sprintf in recordmcount Steven Rostedt
2016-01-05 17:17 ` [PATCH 2/2] tracing: Fix setting of start_index in find_next() 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=20160105171715.485344115@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