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: A couple more small fixes for 4.15
Date: Fri, 19 Jan 2018 12:41:31 -0500	[thread overview]
Message-ID: <20180119174131.963752801@goodmis.org> (raw)


Linus,

Two more small fixes

 - The conversion of enums into their actual numbers to display
   in the event format file had an off-by-one bug, that could cause
   an enum not to be converted, and break user space parsing tools.

 - A fix to a previous fix to bring back the context recursion checks.
   The interrupt case checks for NMI, IRQ and softirq, but the softirq
   returned the same number regardless if it was set or not, although
   the logic would force it to be set if it were hit.

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


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

Tag SHA1: 731752ff22e86fd5a139de2f1a300cd9746ac870
Head SHA1: 1ebe1eaf2f02784921759992ae1fde1a9bec8fd0


Steven Rostedt (VMware) (2):
      ring-buffer: Fix duplicate results in mapping context to bits in recursive lock
      tracing: Fix converting enum's from the map in trace_event_eval_update()

----
 kernel/trace/ring_buffer.c  |  3 +--
 kernel/trace/trace_events.c | 16 +++++++++++++++-
 2 files changed, 16 insertions(+), 3 deletions(-)

             reply	other threads:[~2018-01-19 17:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 17:41 Steven Rostedt [this message]
2018-01-19 17:41 ` [PATCH 1/2] ring-buffer: Fix duplicate results in mapping context to bits in recursive lock Steven Rostedt
2018-01-19 17:41 ` [PATCH 2/2] tracing: Fix converting enums from the map in trace_event_eval_update() 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=20180119174131.963752801@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