Linux Trace Kernel
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 8/9] tracing/filters: Terminate filter string at first newline
Date: Mon, 26 Oct 2026 16:49:57 -0400	[thread overview]
Message-ID: <20261026164957.0e498c52@gandalf.local.home> (raw)
In-Reply-To: <179291750264.492959.17808238344327959450.stgit@devnote2>

On Sun, 25 Oct 2026 17:38:22 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:

> From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> 
> Each trace event or subsystem only holds a single filter, and
> append_filter_err() / tracing_log_err() caret placement assumes a
> single-line filter string. However, apply_event_filter() and
> apply_subsystem_event_filter() only call strstrip(), which strips
> trailing newlines but leaves embedded newlines intact.
> 
> An embedded newline in a filter string (for example inside 'CPUS{0\n"}')
> causes cpulist_parse() / bitmap_parselist() to treat '\n' as the end of
> the cpulist and ignore trailing characters before '}', desynchronizing
> quote tracking between calc_stack() and parse_pred() and misaligning
> error_log caret reporting.
> 
> Terminate filter_string at the first '\n' in apply_event_filter(),
> apply_subsystem_event_filter(), and create_filter_start() so only the
> first line is parsed.

How about also checking if there's any non white space after the newline,
and if so, fail the filter outright with -EINVAL?

-- Steve


> 
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> ---
>  kernel/trace/trace_events_filter.c |   15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/kernel/trace/trace_events_filter.c b/kernel/trace/trace_events_filter.c
> index 8d7fb6e9d7f8..14afcca7a444 100644
> --- a/kernel/trace/trace_events_filter.c
> +++ b/kernel/trace/trace_events_filter.c
> @@ -2426,10 +2426,15 @@ static int create_filter_start(char *filter_string, bool set_str,
>  	struct event_filter *filter;
>  	struct filter_parse_error *pe = NULL;
>  	int err = 0;
> +	char *p;
>  
>  	if (WARN_ON_ONCE(*pse || *filterp))
>  		return -EINVAL;
>  
> +	p = strchr(filter_string, '\n');
> +	if (p)
> +		*p = '\0';
> +
>  	filter = kzalloc_obj(*filter);
>  	if (filter && set_str) {
>  		filter->filter_string = kstrdup(filter_string, GFP_KERNEL);
> @@ -2543,11 +2548,16 @@ int apply_event_filter(struct trace_event_file *file, char *filter_string)
>  {
>  	struct trace_event_call *call = file->event_call;
>  	struct event_filter *filter = NULL;
> +	char *p;
>  	int err;
>  
>  	if (file->flags & EVENT_FILE_FL_FREED)
>  		return -ENODEV;
>  
> +	p = strchr(filter_string, '\n');
> +	if (p)
> +		*p = '\0';
> +
>  	if (!strcmp(strstrip(filter_string), "0")) {
>  		filter_disable(file);
>  		filter = event_filter(file);
> @@ -2595,6 +2605,7 @@ int apply_subsystem_event_filter(struct trace_subsystem_dir *dir,
>  	struct trace_array *tr = dir->tr;
>  	struct event_filter *filter = NULL;
>  	int err = 0;
> +	char *p;
>  
>  	guard(mutex)(&event_mutex);
>  
> @@ -2602,6 +2613,10 @@ int apply_subsystem_event_filter(struct trace_subsystem_dir *dir,
>  	if (!dir->nr_events)
>  		return -ENODEV;
>  
> +	p = strchr(filter_string, '\n');
> +	if (p)
> +		*p = '\0';
> +
>  	if (!strcmp(strstrip(filter_string), "0")) {
>  		filter_free_subsystem_preds(dir, tr);
>  		remove_filter_string(system->filter);


  reply	other threads:[~2026-10-26 20:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-25  8:37 [PATCH v2 0/9] tracing/filters: Fix event filter parsing and matching bugs Masami Hiramatsu (Google)
2026-10-25  8:37 ` [PATCH v2 1/9] tracing/filters: Fix MATCH_END_ONLY regex matching for fixed-size strings Masami Hiramatsu (Google)
2026-10-26 23:11   ` Masami Hiramatsu (Google)
2026-10-25  8:37 ` [PATCH v2 2/9] tracing/filters: Fix false success return in process_system_preds() Masami Hiramatsu (Google)
2026-10-25  8:37 ` [PATCH v2 3/9] tracing/filters: Handle out-of-range CPU for OP_NE in cpumask comparison Masami Hiramatsu (Google)
2026-10-25  8:37 ` [PATCH v2 4/9] tracing/filters: Report parse error on all -EINVAL paths in filter parsing Masami Hiramatsu (Google)
2026-10-25  8:37 ` [PATCH v2 5/9] tracing/filters: Fix function event operand parsing in parse_pred() Masami Hiramatsu (Google)
2026-10-26 20:32   ` Steven Rostedt
2026-10-26 23:37     ` Masami Hiramatsu (Google)
2026-10-25  8:38 ` [PATCH v2 6/9] tracing/filters: Skip second character of '&&' and '||' in calc_stack() Masami Hiramatsu (Google)
2026-10-26 20:47   ` Steven Rostedt
2026-10-26 23:50     ` Masami Hiramatsu (Google)
2026-10-27  0:12       ` Masami Hiramatsu (Google)
2026-10-27 12:45         ` Steven Rostedt
2026-10-25  8:38 ` [PATCH v2 7/9] tracing/filters: Reject unsupported field sizes in parse_pred() Masami Hiramatsu (Google)
2026-10-25  8:38 ` [PATCH v2 8/9] tracing/filters: Terminate filter string at first newline Masami Hiramatsu (Google)
2026-10-26 20:49   ` Steven Rostedt [this message]
2026-10-26 23:53     ` Masami Hiramatsu (Google)
2026-10-25  8:38 ` [PATCH v2 9/9] selftests/ftrace: Add event filter syntax check test case Masami Hiramatsu (Google)
2026-10-25  8:46   ` sashiko-bot

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=20261026164957.0e498c52@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=shuah@kernel.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