Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751492AbeAOXUG (ORCPT + 1 other); Mon, 15 Jan 2018 18:20:06 -0500 Received: from mail.kernel.org ([198.145.29.99]:39460 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750750AbeAOXUD (ORCPT ); Mon, 15 Jan 2018 18:20:03 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 309CA21778 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Mon, 15 Jan 2018 18:20:00 -0500 From: Steven Rostedt To: changbin.du@intel.com Cc: jolsa@redhat.com, peterz@infradead.org, mingo@redhat.com, alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org Subject: Re: [PATCH v2 1/3] tracing: detect the string termination character when parsing user input string Message-ID: <20180115182000.531487c2@gandalf.local.home> In-Reply-To: <1516016474-5581-2-git-send-email-changbin.du@intel.com> References: <1516016474-5581-1-git-send-email-changbin.du@intel.com> <1516016474-5581-2-git-send-email-changbin.du@intel.com> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Mon, 15 Jan 2018 19:41:12 +0800 changbin.du@intel.com wrote: > From: Changbin Du > > The usersapce can give a '\0' terminated C string in the input buffer. > Before this change, trace_get_user() will return a parsed string "\0" in > below case which is not expected (expects it skip all inputs) and cause the > caller failed. The above totally does not parse (no pun intended). Are you trying to say: "User space can pass in a C nul character '\0' along with its input. The function trace_get_user() will try to process it as a normal character, and that will fail to parse. > > open("/sys/kernel/debug/tracing//set_ftrace_pid", O_WRONLY|O_TRUNC) = 3 > write(3, " \0", 2) = -1 EINVAL (Invalid argument) > > while parse can handle spaces, so below works. > > $ echo "" > set_ftrace_pid > $ echo " " > set_ftrace_pid > $ echo -n " " > set_ftrace_pid > > This patch try to make the parser '\0' aware to fix such issue. When parser > sees a '\0' it stops further parsing. With this change, write(3, " \0", 2) > will work. The above should be something like: "Have the parser stop on '\0' and cease any further parsing. Only process the characters up to the nul '\0' character and do not process it." -- Steve > > Signed-off-by: Changbin Du > > --- > v2: Stop parsing when '\0' found. > --- > kernel/trace/trace.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c > index 2a8d8a2..144d08e 100644 > --- a/kernel/trace/trace.c > +++ b/kernel/trace/trace.c > @@ -1237,7 +1237,7 @@ int trace_get_user(struct trace_parser *parser, const char __user *ubuf, > } > > /* only spaces were written */ > - if (isspace(ch)) { > + if (isspace(ch) || !ch) { > *ppos += read; > ret = read; > goto out; > @@ -1247,7 +1247,7 @@ int trace_get_user(struct trace_parser *parser, const char __user *ubuf, > } > > /* read the non-space input */ > - while (cnt && !isspace(ch)) { > + while (cnt && !isspace(ch) && ch) { > if (parser->idx < parser->size - 1) > parser->buffer[parser->idx++] = ch; > else { > @@ -1262,7 +1262,7 @@ int trace_get_user(struct trace_parser *parser, const char __user *ubuf, > } > > /* We either got finished input or we have to wait for another call. */ > - if (isspace(ch)) { > + if (isspace(ch) || !ch) { > parser->buffer[parser->idx] = 0; > parser->cont = false; > } else if (parser->idx < parser->size - 1) {