[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090226053240.607719846@goodmis.org>
Date: Thu, 26 Feb 2009 00:32:40 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: linux-kernel@...r.kernel.org
Cc: Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
"H. Peter Anvin" <hpa@...or.com>
Subject: [PATCH v2 0/5] [RFC] copy_strtok_from_user
This is the second series of the uaccess code.
Changes in v2:
- moved probe_kernel_* functions to lib/uaccess.c
- renamed copy_word_from_user to copy_strtok_from_user.
- changed copy_strtok_from_user to pass in a delimiter string.
ftrace defines SPACE to be ' \t\r\n'.
Ingo,
I added your copy right to lib/uaccess.c since git blame shows you
as the author of the probe_kernel_* code. Also, is it OK that I
added the "GPL v2" line in that file as well?
Andrew,
Since you are, in essence, the memory maintainer, could you give
your Acked-by: to the copy_strtok_from_user code.
The probe_kernel code is still EXPORT_SYMBOL_GPL, and I added
that too to copy_strtok_from_user. Are there any objections to that?
-- 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 (5):
uaccess: move probe_kernel_* functions to lib/uaccess.c
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/uaccess.h | 5 +
kernel/trace/ftrace.c | 155 +++++++++++++++---------------
kernel/trace/trace.h | 2 +
kernel/trace/trace_events.c | 78 +++++++--------
lib/Makefile | 3 +-
lib/uaccess.c | 229 +++++++++++++++++++++++++++++++++++++++++++
mm/Makefile | 2 +-
mm/maccess.c | 55 ----------
8 files changed, 351 insertions(+), 178 deletions(-)
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists