From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ilkka Koskinen <ilkka@os.amperecomputing.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
James Clark <james.clark@arm.com>,
Ian Rogers <irogers@google.com>,
Evgeny Pistun <kotborealis@awooo.ru>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] perf data convert: Fix segfault when converting to json when cpu_desc isn't set
Date: Sat, 24 Feb 2024 12:49:35 -0300 [thread overview]
Message-ID: <ZdoQD1UJkl-IFSJG@x1> (raw)
In-Reply-To: <20240223220458.15282-1-ilkka@os.amperecomputing.com>
On Fri, Feb 23, 2024 at 02:04:58PM -0800, Ilkka Koskinen wrote:
> Arm64 doesn't have Model in /proc/cpuinfo and, thus, cpu_desc doesn't get
> assigned.
>
> Running
> $ perf data convert --to-json perf.data.json
>
> ends up calling output_json_string() with NULL pointer, which causes a
> segmentation fault.
>
> Signed-off-by: Ilkka Koskinen <ilkka@os.amperecomputing.com>
Acked-by: Arnaldo Carvalho de Melo <acme@redhat.com>
- Arnaldo
> ---
>
> v1:
> - https://lore.kernel.org/all/20240111232923.8138-1-ilkka@os.amperecomputing.com/
> v2:
> - Changed the patch based on James's comments.
> v3:
> - The architecture is checked from the actual data file to allow one to do
> conversion on another system. (thanks to James for the feedback)
> - https://lore.kernel.org/all/20240117215101.77713-1-ilkka@os.amperecomputing.com/
> v4:
> - Made the fix more generic in case there are other architectures where cpu_desc
> isn't assigned as asked by Namhyung
> - Rephrased the subject line
> ---
>
> tools/perf/util/data-convert-json.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/data-convert-json.c b/tools/perf/util/data-convert-json.c
> index 5bb3c2ba95ca..09d57efd2d9d 100644
> --- a/tools/perf/util/data-convert-json.c
> +++ b/tools/perf/util/data-convert-json.c
> @@ -284,7 +284,9 @@ static void output_headers(struct perf_session *session, struct convert_json *c)
> output_json_key_string(out, true, 2, "os-release", header->env.os_release);
> output_json_key_string(out, true, 2, "arch", header->env.arch);
>
> - output_json_key_string(out, true, 2, "cpu-desc", header->env.cpu_desc);
> + if (header->env.cpu_desc)
> + output_json_key_string(out, true, 2, "cpu-desc", header->env.cpu_desc);
> +
> output_json_key_string(out, true, 2, "cpuid", header->env.cpuid);
> output_json_key_format(out, true, 2, "nrcpus-online", "%u", header->env.nr_cpus_online);
> output_json_key_format(out, true, 2, "nrcpus-avail", "%u", header->env.nr_cpus_avail);
> --
> 2.43.0
next prev parent reply other threads:[~2024-02-24 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 22:04 [PATCH v4] perf data convert: Fix segfault when converting to json when cpu_desc isn't set Ilkka Koskinen
2024-02-24 15:49 ` Arnaldo Carvalho de Melo [this message]
2024-02-27 17:25 ` 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=ZdoQD1UJkl-IFSJG@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ilkka@os.amperecomputing.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kotborealis@awooo.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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 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).