All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Rikard Falkeborn <rikard.falkeborn@gmail.com>,
	linux-kernel@vger.kernel.org, tstoyanov@vmware.com,
	Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH] tools lib traceevent: Fix missing equality check for strcmp
Date: Tue, 9 Apr 2019 11:54:23 -0300	[thread overview]
Message-ID: <20190409145423.GD2581@redhat.com> (raw)
In-Reply-To: <20190409092122.2e8f62f0@gandalf.local.home>

Em Tue, Apr 09, 2019 at 09:21:22AM -0400, Steven Rostedt escreveu:
> 
> Hi Rikard,
> 
> On Tue,  9 Apr 2019 11:15:29 +0200
> Rikard Falkeborn <rikard.falkeborn@gmail.com> wrote:
> 
> > There was a missing comparison with 0 when checking if type is "s64" or
> > "u64". Therefore, the body of the if-statement was entered if "type" was
> > "u64" or not "s64", which made the first strcmp() redundant since if
> > type is "u64", it's not "s64".
> > 
> > If type is "s64", the body of the if-statement is not entered but since the
> > remainder of the function consists of if-statements which will not be
> > entered if type is "s64", we will just return "val", which is correct,
> > albeit at the cost of a few more calls to strcmp(), i.e., it will behave
> > just as if the if-statement was entered.
> > 
> > If type is neither "s64" or "u64", the body of the if-statement will be
> > entered incorrectly and "val" returned. This means that any type that is
> > checked after "s64" and "u64" is handled the same way as "s64" and
> > "u64", i.e., the limiting of "val" to fit in for example "s8" is never
> > reached.
> > 
> > This was introduced in the kernel tree when the sources were copied from
> > trace-cmd in commit f7d82350e597 ("tools/events: Add files to create
> > libtraceevent.a"), and in the trace-cmd repo in 1cdbae6035cei ("Implement
> > typecasting in parser") when the function was introduced, i.e., it has
> > always behaved the wrong way.
> > 
> > Detected by cppcheck.
> 
> Nice. Thanks for this.
> 
> > 
> > Fixes: f7d82350e597 ("tools/events: Add files to create libtraceevent.a")
> > Signed-off-by: Rikard Falkeborn <rikard.falkeborn@gmail.com>
> 
> Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> 
> Arnaldo,
> 
> Care to pull this in?

Sure, thanks.

- Arnaldo
 
> Thanks!
> 
> -- Steve
> 
> > ---
> > I have only compile tested the patch but it should be correct. I don't
> > know if any other problems will surface due to this though.
> > ---
> >  tools/lib/traceevent/event-parse.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/tools/lib/traceevent/event-parse.c b/tools/lib/traceevent/event-parse.c
> > index 87494c7c619d..981c6ce2da2c 100644
> > --- a/tools/lib/traceevent/event-parse.c
> > +++ b/tools/lib/traceevent/event-parse.c
> > @@ -2233,7 +2233,7 @@ eval_type_str(unsigned long long val, const char *type, int pointer)
> >  		return val & 0xffffffff;
> >  
> >  	if (strcmp(type, "u64") == 0 ||
> > -	    strcmp(type, "s64"))
> > +	    strcmp(type, "s64") == 0)
> >  		return val;
> >  
> >  	if (strcmp(type, "s8") == 0)

  reply	other threads:[~2019-04-09 14:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09  9:15 [PATCH] tools lib traceevent: Fix missing equality check for strcmp Rikard Falkeborn
2019-04-09 13:21 ` Steven Rostedt
2019-04-09 14:54   ` Arnaldo Carvalho de Melo [this message]
2019-04-12 16:39 ` [tip:perf/urgent] " tip-bot for Rikard Falkeborn
2019-04-16 15:30 ` tip-bot for Rikard Falkeborn

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=20190409145423.GD2581@redhat.com \
    --to=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rikard.falkeborn@gmail.com \
    --cc=rostedt@goodmis.org \
    --cc=tstoyanov@vmware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.