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>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: [PATCH 0/2] [GIT PULL] tracing: A couple of fixes to tracepoints
Date: Thu, 08 May 2014 17:07:03 -0400 [thread overview]
Message-ID: <20140508210703.464573159@goodmis.org> (raw)
Linus,
This contains two fixes.
The first is a long standing bug that causes bogus data to show up
in the refcnt field of the module_refcnt tracepoint. It was
introduced by a merge conflict resolution back in 2.6.35-rc days.
The result should be refcnt = incs - decs, but instead it did
refcnt = incs + decs.
The second fix is to a bug that was introduced in this merge window
that allowed for a tracepoint funcs pointer to be used after it
was freed. Moving the location of where the probes are released
solved the problem.
Please pull the latest trace-fixes-v3.15-rc4-v2 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-fixes-v3.15-rc4-v2
Tag SHA1: 3c46db2195fb760afba9f01a495557e78ca8226e
Head SHA1: 8058bd0faad860e75547cc5cb5d4ade016247a79
Mathieu Desnoyers (1):
tracepoint: Fix use of tracepoint funcs after rcu free
Romain Izard (1):
trace: module: Maintain a valid user count
----
include/trace/events/module.h | 2 +-
kernel/tracepoint.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
next reply other threads:[~2014-05-08 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 21:07 Steven Rostedt [this message]
2014-05-08 21:07 ` [PATCH 1/2] trace: module: Maintain a valid user count Steven Rostedt
2014-05-08 21:07 ` [PATCH 2/2] tracepoint: Fix use of tracepoint funcs after rcu free 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=20140508210703.464573159@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--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