From: Tom Zanussi <zanussi@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: rostedt@goodmis.org, axelrasmussen@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] tracing: Fix parse_synth_field() error handling
Date: Thu, 01 Oct 2020 16:50:02 -0500 [thread overview]
Message-ID: <ef7e77e6e1ab23dacb5bf43bf52f4131fcdec059.camel@kernel.org> (raw)
In-Reply-To: <20201001142723.66b8f3d7d6f7df803044c567@kernel.org>
Hi Masami,
On Thu, 2020-10-01 at 14:27 +0900, Masami Hiramatsu wrote:
> Hi Tom,
>
> On Wed, 30 Sep 2020 13:40:51 -0500
> Tom Zanussi <zanussi@kernel.org> wrote:
>
> > synth_field_size() returns either a positive size or an error (zero
> > or
> > a negative value). However, the existing code assumes the only
> > error
> > value is 0. It doesn't handle negative error codes, as it assigns
> > directly to field->size (a size_t; unsigned), thereby interpreting
> > the
> > error code as a valid size instead.
> >
> > Do the test before assignment to field->size.
>
> This looks good to me. And I guess it is a kind of bugfix which
> should be backported?
> (doesn't this need a Fixes tag?)
Yep, thanks for pointing that out.
>
> Reviewed-by: Masami Hiramatsu <mhiramat@kernel.org>
>
Thanks!
Tom
> Thank you,
>
> >
> > [ axelrasmussen@google.com: changelog addition, first paragraph
> > above ]
> >
> > Signed-off-by: Tom Zanussi <zanussi@kernel.org>
> > ---
> > kernel/trace/trace_events_synth.c | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/kernel/trace/trace_events_synth.c
> > b/kernel/trace/trace_events_synth.c
> > index a9cd7793f7ea..fa8a99828f41 100644
> > --- a/kernel/trace/trace_events_synth.c
> > +++ b/kernel/trace/trace_events_synth.c
> > @@ -465,6 +465,7 @@ static struct synth_field
> > *parse_synth_field(int argc, const char **argv,
> > struct synth_field *field;
> > const char *prefix = NULL, *field_type = argv[0], *field_name,
> > *array;
> > int len, ret = 0;
> > + ssize_t size;
> >
> > if (field_type[0] == ';')
> > field_type++;
> > @@ -520,11 +521,12 @@ static struct synth_field
> > *parse_synth_field(int argc, const char **argv,
> > field->type[len - 1] = '\0';
> > }
> >
> > - field->size = synth_field_size(field->type);
> > - if (!field->size) {
> > + size = synth_field_size(field->type);
> > + if (size <= 0) {
> > ret = -EINVAL;
> > goto free;
> > }
> > + field->size = size;
> >
> > if (synth_field_is_string(field->type))
> > field->is_string = true;
> > --
> > 2.17.1
> >
>
>
next prev parent reply other threads:[~2020-10-01 21:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 18:40 [PATCH v2 0/3] tracing: Add dynamic strings for synthetic events Tom Zanussi
2020-09-30 18:40 ` [PATCH v2 1/3] tracing: Change STR_VAR_MAX_LEN Tom Zanussi
2020-09-30 22:45 ` Axel Rasmussen
2020-10-01 21:50 ` Tom Zanussi
2020-09-30 18:40 ` [PATCH v2 2/3] tracing: Fix parse_synth_field() error handling Tom Zanussi
2020-10-01 5:27 ` Masami Hiramatsu
2020-10-01 21:50 ` Tom Zanussi [this message]
2020-09-30 18:40 ` [PATCH v2 3/3] tracing: Add support for dynamic strings to synthetic events Tom Zanussi
2020-10-02 7:17 ` Masami Hiramatsu
2020-10-02 22:06 ` Tom Zanussi
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=ef7e77e6e1ab23dacb5bf43bf52f4131fcdec059.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--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
Powered by JetHome