Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751124AbeAPJLT (ORCPT + 1 other); Tue, 16 Jan 2018 04:11:19 -0500 Received: from mga05.intel.com ([192.55.52.43]:39044 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750821AbeAPJLR (ORCPT ); Tue, 16 Jan 2018 04:11:17 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,367,1511856000"; d="scan'208";a="10759522" From: changbin.du@intel.com To: rostedt@goodmis.org 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, Changbin Du Subject: [PATCH v3 0/3] tracing: Fix the parser when processing strings w/ or w/o terminated '\0' Date: Tue, 16 Jan 2018 17:02:27 +0800 Message-Id: <1516093350-12045-1-git-send-email-changbin.du@intel.com> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: From: Changbin Du I found there are some problems in the tracing parser when I investiage the root cause of issues mentioned in below patch. https://patchwork.kernel.org/patch/10132953/ This serials can fix them. v3: Polish commit msg from Steven Rostedt. v2: - Drop 1 old patch and add a new one. - Stop parsing when '\0' found. Changbin Du (3): tracing: detect the string termination character when parsing user input string tracing: clear parser->idx if parser gets nothing tracing: make sure the parsed string always terminates with '\0' kernel/trace/ftrace.c | 2 -- kernel/trace/trace.c | 14 +++++++------- kernel/trace/trace_events.c | 2 -- 3 files changed, 7 insertions(+), 11 deletions(-) -- 2.7.4