From: Chen Yu <yu.c.chen@intel.com>
To: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
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>,
Kan Liang <kan.liang@linux.intel.com>, <acme@redhat.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] perf sched map: Add command-name, fuzzy-name options to filter the output map
Date: Tue, 18 Jun 2024 21:52:15 +0800 [thread overview]
Message-ID: <ZnGRDyWrAUHnghtb@chenyu5-mobl2> (raw)
In-Reply-To: <20240617125006.31654-1-vineethr@linux.ibm.com>
On 2024-06-17 at 18:19:30 +0530, Madadi Vineeth Reddy wrote:
> +static struct CommandList *parse_commands(const char *commands)
> +{
> + char *commands_copy = strdup(commands);
Should we check if commands_copy is NULL in case of allocation failure?
> + char *token = strtok(commands_copy, ",");
> + struct CommandList *cmd_list = malloc(sizeof(struct CommandList));
> +
> + if (cmd_list == NULL)
> + return NULL;
> +
> + cmd_list->command_count = 0;
> + cmd_list->command_list = NULL;
> +
> + while (token != NULL) {
> + cmd_list->command_list = realloc(cmd_list->command_list, sizeof(char *)
> + *(cmd_list->command_count + 1));
> + cmd_list->command_list[cmd_list->command_count] = strdup(token);
ditto.
thanks,
Chenyu
next prev parent reply other threads:[~2024-06-18 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 12:49 Madadi Vineeth Reddy
2024-06-18 13:52 ` Chen Yu [this message]
2024-06-18 16:30 ` Madadi Vineeth Reddy
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=ZnGRDyWrAUHnghtb@chenyu5-mobl2 \
--to=yu.c.chen@intel.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=atrajeev@linux.vnet.ibm.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=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=vineethr@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®