From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: [PATCH v3 0/6] [RFC] copy_strtok_from_user
Date: Thu, 26 Feb 2009 13:54:19 -0500 [thread overview]
Message-ID: <20090226185419.371469287@goodmis.org> (raw)
Changes in v3:
- created strtok_r for kernel.
- Simplified copy_strtok_from_user by using strtok_r
- updated the rest of the code to handle the above changes
I tested both the strtok_r and copy_strtok_from_user with this user app:
http://www.kernel.org/pub/linux/kernel/people/rostedt/copy_strtok_from_user.c
Results of the test are here:
http://www.kernel.org/pub/linux/kernel/people/rostedt/copy_strtok_test.txt
I added a "#undef strtok_r" after the strtok_r function and ran it again
to make sure the output was still the same, and it was.
Andrew, If this version is fine with you, could you ack the patches that
create the strtok_r and copy_strtok_from_user functions.
Thanks,
-- Steve
The following patches are in:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
branch: tip/tracing/uaccess
Steven Rostedt (6):
uaccess: move probe_kernel_* functions to lib/uaccess.c
string: add strtok_r to kernel
uaccess: add copy_strtok_from_user
tracing: convert event_trace to use copy_strtok_from_user
tracing: convert ftrace_regex_write to use copy_strtok_from_user
tracing: convert ftrace_graph_write to use copy_strtok_from_user
----
include/linux/string.h | 3 +
include/linux/uaccess.h | 4 +
kernel/trace/ftrace.c | 149 ++++++++++++++++---------------
kernel/trace/trace.h | 2 +
kernel/trace/trace_events.c | 69 +++++---------
lib/Makefile | 3 +-
lib/string.c | 43 +++++++++
lib/uaccess.c | 205 +++++++++++++++++++++++++++++++++++++++++++
mm/Makefile | 2 +-
mm/maccess.c | 55 ------------
10 files changed, 361 insertions(+), 174 deletions(-)
--
next reply other threads:[~2009-02-26 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 18:54 Steven Rostedt [this message]
2009-02-26 18:54 ` [PATCH v3 1/6] uaccess: move probe_kernel_* functions to lib/uaccess.c Steven Rostedt
2009-02-26 18:54 ` [PATCH v3 2/6] string: add strtok_r to kernel Steven Rostedt
2009-02-26 18:54 ` [PATCH v3 3/6] uaccess: add copy_strtok_from_user Steven Rostedt
2009-02-26 18:54 ` [PATCH v3 4/6] tracing: convert event_trace to use copy_strtok_from_user Steven Rostedt
2009-02-26 18:54 ` [PATCH v3 5/6] tracing: convert ftrace_regex_write " Steven Rostedt
2009-02-26 18:54 ` [PATCH v3 6/6] tracing: convert ftrace_graph_write " 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=20090226185419.371469287@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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