linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "Fernando F. Mancera" <ffmancera@riseup.net>
Cc: linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing/probes: fix traceprobe out-of-bounds argument allocation
Date: Mon, 26 Aug 2024 08:56:59 +0900	[thread overview]
Message-ID: <20240826085659.939bde641e4bf13249dec6ec@kernel.org> (raw)
In-Reply-To: <fc31cca4-bec6-461c-9843-b4121ac1ba20@riseup.net>

On Sun, 25 Aug 2024 19:06:22 +0200
"Fernando F. Mancera" <ffmancera@riseup.net> wrote:

> Hi,
> 
> On 25/08/2024 09:41, Masami Hiramatsu (Google) wrote:
> > Hi,
> > 
> > On Tue, 13 Aug 2024 13:25:40 -0400
> > Fernando Fernandez Mancera <ffmancera@riseup.net> wrote:
> > 
> >> When initializing trace_probes::nr_args, make sure the maximum number of
> >> probe arguments is honored. Oherwise, we can hit a NULL pointer
> >> dereferences in multiple situations like on traceprobe_set_print_fmt().
> >>
> >> Link: https://bugzilla.redhat.com/2303876
> > 
> > Sorry for replying later. I'm not sure why but I did not found this in my mbox...
> > 
> 
> No worries!
> 
> > Anyway, trace_probe_init() should return -E2BIG in this case because
> > it is actuall wrong value.
> > 
> > Can you update your patch?
> > 
> 
> I agree this is the right solution but it would mean a change in 
> behavior. Is that fine? Before merging 035ba76014c0, it was writing up 
> to the maximum number of arguments and ignoring the rest. If you confirm 
> it is fine to change the behavior, I will update the patch.

Yes, I think this is the better behavior for users too, rather than
silently droping some arguments.
We also need to handle this error code in callsite and log an error,
and add a testcase in the syntax error testcase. But that should be done
in another series. We should fix this first.

Thank you,


> 
> Thank you!
> 
> > Thank you,
> > 
> > 
> >>
> >> Fixes: 035ba76014c0 ("tracing/probes: cleanup: Set trace_probe::nr_args at trace_probe_init")
> >> Signed-off-by: Fernando Fernandez Mancera <ffmancera@riseup.net>
> >> ---
> >>   kernel/trace/trace_probe.c | 8 ++++++--
> >>   1 file changed, 6 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/kernel/trace/trace_probe.c b/kernel/trace/trace_probe.c
> >> index 39877c80d6cb..f577b5e71026 100644
> >> --- a/kernel/trace/trace_probe.c
> >> +++ b/kernel/trace/trace_probe.c
> >> @@ -2043,10 +2043,14 @@ int trace_probe_init(struct trace_probe *tp, const char *event,
> >>   		goto error;
> >>   	}
> >>   
> >> -	tp->nr_args = nargs;
> >> +	if (nargs > MAX_TRACE_ARGS)
> >> +		tp->nr_args = MAX_TRACE_ARGS;
> >> +	else
> >> +		tp->nr_args = nargs;
> >> +
> >>   	/* Make sure pointers in args[] are NULL */
> >>   	if (nargs)
> >> -		memset(tp->args, 0, sizeof(tp->args[0]) * nargs);
> >> +		memset(tp->args, 0, sizeof(tp->args[0]) * tp->nr_args);
> >>   
> >>   	return 0;
> >>   
> > 
> > 


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

  reply	other threads:[~2024-08-25 23:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13 17:25 [PATCH] tracing/probes: fix traceprobe out-of-bounds argument allocation Fernando Fernandez Mancera
2024-08-25  7:41 ` Masami Hiramatsu
2024-08-25 17:06   ` Fernando F. Mancera
2024-08-25 23:56     ` Masami Hiramatsu [this message]
2024-08-26 14:58       ` Fernando F. Mancera
2024-09-04 22:19       ` Fernando F. Mancera
2024-10-22  5:40         ` Masami Hiramatsu
2024-10-22 13:47           ` Masami Hiramatsu
2024-10-23  8:48           ` Fernando F. Mancera

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=20240826085659.939bde641e4bf13249dec6ec@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=ffmancera@riseup.net \
    --cc=linux-trace-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).