From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>,
Kan Liang <kan.liang@linux.intel.com>
Cc: Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org,
kernel test robot <oliver.sang@intel.com>
Subject: [PATCH 3/4] perf tools: Fix a compiler warning of NULL pointer
Date: Fri, 21 Jun 2024 10:05:27 -0700 [thread overview]
Message-ID: <20240621170528.608772-4-namhyung@kernel.org> (raw)
In-Reply-To: <20240621170528.608772-1-namhyung@kernel.org>
A compiler warning on the second argument of bsearch() should not be
NULL, but there's a case we might pass it. Let's return early if we
don't have any DSOs to search in __dsos__find_by_longname_id().
util/dsos.c:184:8: runtime error: null pointer passed as argument 2, which is declared to never be null
Reported-by: kernel test robot <oliver.sang@intel.com>
Closes: https://lore.kernel.org/oe-lkp/202406180932.84be448c-oliver.sang@intel.com
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
---
tools/perf/util/dsos.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/perf/util/dsos.c b/tools/perf/util/dsos.c
index ab3d0c01dd63..d5d78bdc56b2 100644
--- a/tools/perf/util/dsos.c
+++ b/tools/perf/util/dsos.c
@@ -164,6 +164,9 @@ static struct dso *__dsos__find_by_longname_id(struct dsos *dsos,
};
struct dso **res;
+ if (dsos->dsos == NULL)
+ return NULL;
+
if (!dsos->sorted) {
if (!write_locked) {
struct dso *dso;
--
2.45.2.741.gdbec12cfda-goog
next prev parent reply other threads:[~2024-06-21 17:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 17:05 [PATCH 0/4] perf tools: Assorted random updates and fixes Namhyung Kim
2024-06-21 17:05 ` [PATCH 1/4] perf report: Fix condition in sort__sym_cmp() Namhyung Kim
2024-06-21 17:05 ` [PATCH 2/4] perf symbol: Simplify kernel module checking Namhyung Kim
2024-06-21 17:05 ` Namhyung Kim [this message]
2024-06-21 17:05 ` [PATCH 4/4] perf mem: Fix a segfault with NULL event->name Namhyung Kim
2024-06-21 20:11 ` Liang, Kan
2024-06-25 5:07 ` Namhyung Kim
2024-06-21 20:14 ` [PATCH 0/4] perf tools: Assorted random updates and fixes Liang, Kan
2024-06-26 4:02 ` Namhyung Kim
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=20240621170528.608772-4-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oliver.sang@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox