mirror of https://lore.kernel.org/lkml/
 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: Two minor updates
Date: Wed, 04 Oct 2017 11:22:36 -0400	[thread overview]
Message-ID: <20171004152236.000114616@goodmis.org> (raw)


Linus,

Two updates.

 - A memory fix with left over code from spliting out ftrace_ops
   and function graph tracer, where the function graph tracer could
   reset the trampoline pointer, leaving the old trampoline not to
   be freed (memory leak).

 - The update to Paul's patch that added the unnecessary READ_ONCE().
   This removes the unnecessary READ_ONCE() instead of having to rebase
   the branch to update the patch that added it.

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


  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.14-rc1-3

Tag SHA1: 3860b8ee2c2850d80277992ba1d0275514ee1238
Head SHA1: f39b536ce9248e9799ff900358d6f073ab2e6c55


Paul E. McKenney (1):
      rcu: Remove extraneous READ_ONCE()s from rcu_irq_{enter,exit}()

Shu Wang (1):
      ftrace: Fix kmemleak in unregister_ftrace_graph

----
 kernel/rcu/tree.c     |  4 ++--
 kernel/trace/ftrace.c | 14 --------------
 2 files changed, 2 insertions(+), 16 deletions(-)

             reply	other threads:[~2017-10-04 15:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04 15:22 Steven Rostedt [this message]
2017-10-04 15:22 ` [PATCH 1/2] ftrace: Fix kmemleak in unregister_ftrace_graph Steven Rostedt
2017-10-04 15:22 ` [PATCH 2/2] rcu: Remove extraneous READ_ONCE()s from rcu_irq_{enter,exit}() 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=20171004152236.000114616@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

Powered by JetHome