Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753670AbeAIKEi (ORCPT + 1 other); Tue, 9 Jan 2018 05:04:38 -0500 Received: from mga01.intel.com ([192.55.52.88]:22519 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753639AbeAIKEe (ORCPT ); Tue, 9 Jan 2018 05:04:34 -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,335,1511856000"; d="scan'208";a="9812781" 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 0/3] tracing: Fix the parser when processing strings w/ or w/o terminated '\0' Date: Tue, 9 Jan 2018 17:55:45 +0800 Message-Id: <1515491748-25926-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. Changbin Du (3): tracing: detect the string termination character when parsing user input string tracing: make sure the parsed string always terminates with '\0' tracing: don't set parser->cont if it has reached the end of input buffer kernel/trace/trace.c | 28 +++++++++++++++++----------- 1 file changed, 17 insertions(+), 11 deletions(-) -- 2.7.4