Linux Trace Kernel
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	pulehui@huawei.com
Subject: Re: [PATCH v2] tracing: Limit access to parser->buffer when trace_get_user failed
Date: Tue, 12 Aug 2025 14:38:12 -0400	[thread overview]
Message-ID: <20250812143812.3df42a3c@gandalf.local.home> (raw)
In-Reply-To: <20250806070109.1320165-1-pulehui@huaweicloud.com>

On Wed,  6 Aug 2025 07:01:09 +0000
Pu Lehui <pulehui@huaweicloud.com> wrote:

> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index 4283ed4e8f59..138212f4ecde 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -1814,9 +1814,11 @@ int trace_get_user(struct trace_parser *parser, const char __user *ubuf,
>  	if (!*ppos)
>  		trace_parser_clear(parser);
>  
> +	parser->fail = false;

This should be set when the parser is initialized.

> +
>  	ret = get_user(ch, ubuf++);
>  	if (ret)
> -		return ret;
> +		goto fail;
>  
>  	read++;
>  	cnt--;
> @@ -1830,7 +1832,7 @@ int trace_get_user(struct trace_parser *parser, const char __user *ubuf,
>  		while (cnt && isspace(ch)) {
>  			ret = get_user(ch, ubuf++);
>  			if (ret)
> -				return ret;
> +				goto fail;
>  			read++;
>  			cnt--;
>  		}
> @@ -1848,12 +1850,14 @@ int trace_get_user(struct trace_parser *parser, const char __user *ubuf,
>  	while (cnt && !isspace(ch) && ch) {
>  		if (parser->idx < parser->size - 1)
>  			parser->buffer[parser->idx++] = ch;
> -		else
> -			return -EINVAL;
> +		else {
> +			ret = -EINVAL;
> +			goto fail;
> +		}
>  
>  		ret = get_user(ch, ubuf++);
>  		if (ret)
> -			return ret;
> +			goto fail;
>  		read++;
>  		cnt--;
>  	}
> @@ -1868,11 +1872,15 @@ int trace_get_user(struct trace_parser *parser, const char __user *ubuf,
>  		/* Make sure the parsed string always terminates with '\0'. */
>  		parser->buffer[parser->idx] = 0;
>  	} else {
> -		return -EINVAL;
> +		ret = -EINVAL;
> +		goto fail;
>  	}
>  
>  	*ppos += read;
>  	return read;
> +fail:
> +	parser->fail = true;

Should have a helper function called: trace_parser_fail(parser) and use
that.

-- Steve


> +	return ret;
>  }
>  
>  /* TODO add a seq_buf_to_buffer() */
> diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
> index 1dbf1d3cf2f1..5072bb25a860 100644
> --- a/kernel/trace/trace.h
> +++ b/kernel/trace/trace.h
> @@ -1292,6 +1292,7 @@ bool ftrace_event_is_function(struct trace_event_call *call);
>   */
>  struct trace_parser {
>  	bool		cont;
> +	bool		fail;
>  	char		*buffer;
>  	unsigned	idx;
>  	unsigned	size;
> @@ -1299,7 +1300,7 @@ struct trace_parser {
>  
>  static inline bool trace_parser_loaded(struct trace_parser *parser)
>  {
> -	return (parser->idx != 0);
> +	return !parser->fail && parser->idx != 0;
>  }
>  
>  static inline bool trace_parser_cont(struct trace_parser *parser)


  reply	other threads:[~2025-08-12 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06  7:01 [PATCH v2] tracing: Limit access to parser->buffer when trace_get_user failed Pu Lehui
2025-08-12 18:38 ` Steven Rostedt [this message]
2025-08-13  3:48   ` Pu Lehui

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=20250812143812.3df42a3c@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=pulehui@huawei.com \
    --cc=pulehui@huaweicloud.com \
    /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