linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Beau Belgrave <beaub@linux.microsoft.com>
Cc: rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
	dcook@linux.microsoft.com, alanau@linux.microsoft.com,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] tracing/user_events: Ensure write index cannot be negative
Date: Tue, 25 Apr 2023 23:43:22 +0900	[thread overview]
Message-ID: <20230425234322.64936672edb26dd2afdb3a55@kernel.org> (raw)
In-Reply-To: <20230411211709.15018-2-beaub@linux.microsoft.com>

On Tue, 11 Apr 2023 14:17:07 -0700
Beau Belgrave <beaub@linux.microsoft.com> wrote:

> The write index indicates which event the data is for and accesses a
> per-file array. The index is passed by user processes during write()
> calls as the first 4 bytes. Ensure that it cannot be negative by
> returning -EINVAL to prevent out of bounds accesses.
> 
> Update ftrace self-test to ensure this occurs properly.
> 
> Fixes: 7f5a08c79df3 ("user_events: Add minimal support for trace_event into ftrace")
> Reported-by: Doug Cook <dcook@linux.microsoft.com>
> Signed-off-by: Beau Belgrave <beaub@linux.microsoft.com>

Looks good to me.

Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>

Thanks!

> ---
>  kernel/trace/trace_events_user.c                  | 3 +++
>  tools/testing/selftests/user_events/ftrace_test.c | 5 +++++
>  2 files changed, 8 insertions(+)
> 
> diff --git a/kernel/trace/trace_events_user.c b/kernel/trace/trace_events_user.c
> index cc8c6d8b69b5..e7dff24aa724 100644
> --- a/kernel/trace/trace_events_user.c
> +++ b/kernel/trace/trace_events_user.c
> @@ -1821,6 +1821,9 @@ static ssize_t user_events_write_core(struct file *file, struct iov_iter *i)
>  	if (unlikely(copy_from_iter(&idx, sizeof(idx), i) != sizeof(idx)))
>  		return -EFAULT;
>  
> +	if (idx < 0)
> +		return -EINVAL;
> +
>  	rcu_read_lock_sched();
>  
>  	refs = rcu_dereference_sched(info->refs);
> diff --git a/tools/testing/selftests/user_events/ftrace_test.c b/tools/testing/selftests/user_events/ftrace_test.c
> index aceafacfb126..91272f9d6fce 100644
> --- a/tools/testing/selftests/user_events/ftrace_test.c
> +++ b/tools/testing/selftests/user_events/ftrace_test.c
> @@ -296,6 +296,11 @@ TEST_F(user, write_events) {
>  	ASSERT_NE(-1, writev(self->data_fd, (const struct iovec *)io, 3));
>  	after = trace_bytes();
>  	ASSERT_GT(after, before);
> +
> +	/* Negative index should fail with EINVAL */
> +	reg.write_index = -1;
> +	ASSERT_EQ(-1, writev(self->data_fd, (const struct iovec *)io, 3));
> +	ASSERT_EQ(EINVAL, errno);
>  }
>  
>  TEST_F(user, write_fault) {
> -- 
> 2.25.1
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2023-04-25 14:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 21:17 [PATCH 0/3] tracing/user_events: Fixes and improvements for 6.4 Beau Belgrave
2023-04-11 21:17 ` [PATCH 1/3] tracing/user_events: Ensure write index cannot be negative Beau Belgrave
2023-04-25 14:43   ` Masami Hiramatsu [this message]
2023-04-11 21:17 ` [PATCH 2/3] tracing/user_events: Ensure bit is cleared on unregister Beau Belgrave
2023-04-25  1:39   ` Steven Rostedt
2023-04-25 17:06     ` Beau Belgrave
2023-04-25 17:56       ` Steven Rostedt
2023-04-11 21:17 ` [PATCH 3/3] tracing/user_events: Prevent same address and bit per process Beau Belgrave
2023-04-25  1:41   ` Steven Rostedt

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=20230425234322.64936672edb26dd2afdb3a55@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=alanau@linux.microsoft.com \
    --cc=beaub@linux.microsoft.com \
    --cc=dcook@linux.microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).