From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@linaro.org>
Cc: Ian Rogers <irogers@google.com>,
Namhyung Kim <namhyung@kernel.org>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v1] perf string: Avoid undefined NULL+1
Date: Thu, 12 Dec 2024 15:54:44 -0300 [thread overview]
Message-ID: <Z1sxdMeSD-pWuUOZ@x1> (raw)
In-Reply-To: <9e9a550c-0017-40b0-af14-99f3c926290c@linaro.org>
On Mon, Dec 09, 2024 at 11:49:15AM +0000, James Clark wrote:
> On 20/11/2024 6:52 am, Ian Rogers wrote:
> > While the value NULL+1 is never used it triggers a ubsan
> > warning. Restructure and comment the loop to avoid this.
> > Signed-off-by: Ian Rogers <irogers@google.com>
> > +++ b/tools/perf/util/string.c
> > @@ -254,11 +254,20 @@ char *strpbrk_esc(char *str, const char *stopset)
> > do {
> > ptr = strpbrk(str, stopset);
> > - if (ptr == str ||
> > - (ptr == str + 1 && *(ptr - 1) != '\\'))
> > + if (!ptr) {
> > + /* stopset not in str. */
> > break;
> > + }
> > + if (ptr == str) {
> > + /* stopset character is first in str. */
> > + break;
> > + }
> > + if (ptr == str + 1 && str[0] != '\\') {
> > + /* stopset chacter is second and wasn't preceded by a '\'. */
> > + break;
> > + }
> > str = ptr + 1;
> > - } while (ptr && *(ptr - 1) == '\\' && *(ptr - 2) != '\\');
> > + } while (ptr[-1] == '\\' && ptr[-2] != '\\');
> > return ptr;
> > }
> Reviewed-by: James Clark <james.clark@linaro.org>
Thanks, applied to perf-tools-next,
- Arnaldo
prev parent reply other threads:[~2024-12-12 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 6:52 [PATCH v1] perf string: Avoid undefined NULL+1 Ian Rogers
2024-12-09 11:49 ` James Clark
2024-12-12 18:54 ` Arnaldo Carvalho de Melo [this message]
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=Z1sxdMeSD-pWuUOZ@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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 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.