From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org, namhyung@kernel.org
Subject: [PATCH v2 8/8] trace-cmd libtraceevent: Handle possible strdup() error in tep_add_plugin_path() API
Date: Wed, 15 Jul 2020 05:30:09 +0300 [thread overview]
Message-ID: <20200715023009.2503879-9-tz.stoyanov@gmail.com> (raw)
In-Reply-To: <20200715023009.2503879-1-tz.stoyanov@gmail.com>
Free allocated resources and return -1 in case strdup() fails in
tep_add_plugin_path() API.
Link: https://lore.kernel.org/linux-trace-devel/CAM9d7cgMgqFDvKhs6xwdBSMsaG=3ZG0RtxwgQDCTLGkML1MY4Q@mail.gmail.com/T/#m60f797c012680cc413a98ffdd9136666efcc4ded
Suggested-by: Namhyung Kim <namhyung@kernel.org>
Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
---
lib/traceevent/event-plugin.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/lib/traceevent/event-plugin.c b/lib/traceevent/event-plugin.c
index 841e41c6..4a3f7d3f 100644
--- a/lib/traceevent/event-plugin.c
+++ b/lib/traceevent/event-plugin.c
@@ -666,6 +666,10 @@ int tep_add_plugin_path(struct tep_handle *tep, char *path,
return -1;
dir->path = strdup(path);
+ if (!dir->path) {
+ free(dir);
+ return -1;
+ }
dir->prio = prio;
dir->next = tep->plugins_dir;
tep->plugins_dir = dir;
--
2.26.2
next prev parent reply other threads:[~2020-07-15 2:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 2:30 [PATCH v2 0/8] Few libtraceeevnt fixes, suggested Namhyung Kim Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` [PATCH v2 1/8] trace-cmd libtraceevent: Document tep_load_plugins_hook() Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` [PATCH v2 2/8] trace-cmd libtraceevent: Handle strdup() error in parse_option_name() Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` [PATCH v2 3/8] trace-cmd libtraceevent: Fix typo in tep_plugin_add_option() description Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` [PATCH v2 4/8] trace-cmd libtraceevent: Improve error handling of tep_plugin_add_option() API Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` [PATCH v2 5/8] trace-cmd libtraceevent: Fix broken indentation in parse_ip4_print_args() Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` [PATCH v2 6/8] trace-cmd libtraceevent: Fix type in PRINT_FMT_STING Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` [PATCH v2 7/8] trace-cmd libtraceevent: Fix description of tep_add_plugin_path() API Tzvetomir Stoyanov (VMware)
2020-07-15 2:30 ` Tzvetomir Stoyanov (VMware) [this message]
2020-07-15 2:36 ` [PATCH v2 0/8] Few libtraceeevnt fixes, suggested Namhyung Kim Steven Rostedt
2020-07-15 4:12 ` Tzvetomir Stoyanov
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=20200715023009.2503879-9-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.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).