mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [GIT PULL] tracing: Fixes for v5.5
Date: Tue, 21 Jan 2020 10:05:20 -0500	[thread overview]
Message-ID: <20200121100520.13525c74@gandalf.local.home> (raw)
In-Reply-To: <20200121094906.421206d7@gandalf.local.home>

On Tue, 21 Jan 2020 09:49:06 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:

> Linus,
> 
> Various tracing fixes:
> 
>  - Fix a function comparison warning for a xen trace event macro
>  - Fix a double perf_event linking to a trace_uprobe_filter for multiple events
>  - Fix suspicious RCU warnings in trace event code for using
>     list_for_each_entry_rcu() when the "_rcu" portion wasn't needed.
>  - Fix a bug in the histogram code when using the same variable
>  - Fix a NULL pointer dereference when tracefs lockdown enabled and calling
>     trace_set_default_clock()
> 
> 
> Please pull the latest trace-v5.5-rc6 tree, which can be found at:

Hi Linus,

Hold off on pulling this. Peter just notified me there's an issue with
one of the patches.

-- Steve

> 
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> trace-v5.5-rc6
> 
> Tag SHA1: f920461f2655601c33276a60a2fb39d0b4f24e28
> Head SHA1: bf24daac8f2bd5b8affaec03c2be1d20bcdd6837
> 
> 
> Changbin Du (1):
>       tracing: xen: Ordered comparison of function pointers
> 
> Masami Hiramatsu (2):
>       tracing/uprobe: Fix double perf_event linking on multiprobe uprobe
>       tracing: trigger: Replace unneeded RCU-list traversals
> 
> Masami Ichikawa (1):
>       tracing: Do not set trace clock if tracefs lockdown is in effect
> 
> Steven Rostedt (VMware) (1):
>       tracing: Fix histogram code when expression has same var as value
> 
> ----
>  include/trace/events/xen.h          |   6 +-
>  kernel/trace/trace.c                |   5 ++
>  kernel/trace/trace_events_hist.c    |  63 ++++++++++++++----
>  kernel/trace/trace_events_trigger.c |  20 ++++--
>  kernel/trace/trace_kprobe.c         |   2 +-
>  kernel/trace/trace_probe.c          |   5 +-
>  kernel/trace/trace_probe.h          |   3 +-
>  kernel/trace/trace_uprobe.c         | 124 +++++++++++++++++++++++-------------
>  8 files changed, 163 insertions(+), 65 deletions(-)
> ---------------------------
> diff --git a/include/trace/events/xen.h b/include/trace/events/xen.h
>

  reply	other threads:[~2020-01-21 15:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 14:49 Steven Rostedt
2020-01-21 15:05 ` Steven Rostedt [this message]
2020-01-23 19:30 ` pr-tracker-bot

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=20200121100520.13525c74@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®