From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Tom Zanussi <tom.zanussi@linux.intel.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: [PATCH 0/2] tracing: Fixes to event_triggers patches found by Fengguang's test bot
Date: Sat, 21 Dec 2013 22:07:59 -0500 [thread overview]
Message-ID: <20131222030759.339128630@goodmis.org> (raw)
Tom,
This is the changes I made to fix the reports that Fengguang's kbuild test bot
found. I folded in your change that fixes the bug with -ENODEV used in kernel.h.
Paul,
I've Cc'd you because the second patch is fixing up RCU notation. The filter
is protect by rcu_sched, and the first hunk of the patch is performed
within a rcu_read_lock_sched(), and the second hunk is done on the write
side. The tmp variable holds the old value, the value is updated, and
then the new value gets updated. I emailed you so that you can verify
that this all works.
Thanks!
-- Steve
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
ftrace/core
Head SHA1: 05741e383228a79eeec83644181255d2171f9f7c
Steven Rostedt (Red Hat) (2):
tracing: Add generic tracing_lseek() function
tracing: Fix rcu handling of event_trigger_data filter field
----
include/linux/ftrace.h | 2 --
kernel/trace/ftrace.c | 25 ++++++-------------------
kernel/trace/trace.c | 14 +++++++++-----
kernel/trace/trace.h | 4 +++-
kernel/trace/trace_events_trigger.c | 10 ++++++----
kernel/trace/trace_stack.c | 2 +-
6 files changed, 25 insertions(+), 32 deletions(-)
next reply other threads:[~2013-12-22 3:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 3:07 Steven Rostedt [this message]
2013-12-22 3:08 ` [PATCH 1/2] tracing: Add generic tracing_lseek() function Steven Rostedt
2013-12-22 3:08 ` [PATCH 2/2] tracing: Fix rcu handling of event_trigger_data filter field Steven Rostedt
2014-01-09 1:30 ` Paul E. McKenney
2013-12-23 3:13 ` [PATCH 0/2] tracing: Fixes to event_triggers patches found by Fengguang's test bot Tom Zanussi
2014-01-02 17:11 ` 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=20131222030759.339128630@goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tom.zanussi@linux.intel.com \
/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