From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>
Subject: [for-next][PATCH v2 0/3] tracing: Fixes to syscall tracing
Date: Fri, 20 Jun 2014 06:45:18 -0400 [thread overview]
Message-ID: <20140620104518.722157733@goodmis.org> (raw)
I don't like to do this but I rebased my for-next branch to have
the first (for stable) patch not break other archs. This set passed my
cross compile test as well as my normal tests.
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 0f6af1fe54b371ab6dfc05d963c0356a43c83226
Oleg Nesterov (3):
tracing: Fix syscall_*regfunc() vs copy_process() race
tracing: Change syscall_*regfunc() to check PF_KTHREAD and use for_each_process_thread()
tracing: syscall_regfunc() should not skip kernel threads
----
include/trace/syscall.h | 15 +++++++++++++++
kernel/fork.c | 2 ++
kernel/tracepoint.c | 26 +++++++++++---------------
3 files changed, 28 insertions(+), 15 deletions(-)
next reply other threads:[~2014-06-20 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 10:45 Steven Rostedt [this message]
2014-06-20 10:45 ` [for-next][PATCH v2 1/3] tracing: Fix syscall_*regfunc() vs copy_process() race Steven Rostedt
2014-06-21 1:11 ` Paul E. McKenney
2014-06-21 1:19 ` Steven Rostedt
2014-06-24 6:55 ` Namhyung Kim
2014-06-26 17:49 ` Steven Rostedt
2014-06-20 10:45 ` [for-next][PATCH v2 2/3] tracing: Change syscall_*regfunc() to check PF_KTHREAD and use for_each_process_thread() Steven Rostedt
2014-06-20 10:45 ` [for-next][PATCH v2 3/3] tracing: syscall_regfunc() should not skip kernel threads 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=20140620104518.722157733@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.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