From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xen.org
Cc: Juergen Gross <jgross@suse.com>,
wei.liu2@citrix.com, ian.jackson@eu.citrix.com
Subject: [PATCH v2 2/5] xenstore: add explicit memory context parameter to get_parent()
Date: Mon, 18 Jul 2016 09:31:26 +0200 [thread overview]
Message-ID: <1468827089-9054-3-git-send-email-jgross@suse.com> (raw)
In-Reply-To: <1468827089-9054-1-git-send-email-jgross@suse.com>
Add a parameter to xenstored get_parent() function to explicitly
specify the memory context to be used for allocations. This will make
it easier to avoid memory leaks by using a context which is freed
soon.
When available use a temporary context when calling get_parent(),
otherwise mimic the old behavior by calling get_parent() with the same
argument for both parameters.
Signed-off-by: Juergen Gross <jgross@suse.com>
---
tools/xenstore/xenstored_core.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/tools/xenstore/xenstored_core.c b/tools/xenstore/xenstored_core.c
index 94c809c..9448ee8 100644
--- a/tools/xenstore/xenstored_core.c
+++ b/tools/xenstore/xenstored_core.c
@@ -507,12 +507,12 @@ static enum xs_perm_type perm_for_conn(struct connection *conn,
return perms[0].perms & mask;
}
-static char *get_parent(const char *node)
+static char *get_parent(const void *mem, const char *node)
{
char *slash = strrchr(node + 1, '/');
if (!slash)
- return talloc_strdup(node, "/");
- return talloc_asprintf(node, "%.*s", (int)(slash - node), node);
+ return talloc_strdup(mem, "/");
+ return talloc_asprintf(mem, "%.*s", (int)(slash - node), node);
}
/* What do parents say? */
@@ -521,7 +521,7 @@ static enum xs_perm_type ask_parents(struct connection *conn, const char *name)
struct node *node;
do {
- name = get_parent(name);
+ name = get_parent(name, name);
node = read_node(conn, name);
if (node)
break;
@@ -816,7 +816,7 @@ static struct node *construct_node(struct connection *conn, const char *name)
const char *base;
unsigned int baselen;
struct node *parent, *node;
- char *children, *parentname = get_parent(name);
+ char *children, *parentname = get_parent(name, name);
/* If parent doesn't exist, create it. */
parent = read_node(conn, parentname);
@@ -1036,7 +1036,7 @@ static int _rm(struct connection *conn, struct node *node, const char *name)
/* Delete from parent first, then if we crash, the worst that can
happen is the child will continue to take up space, but will
otherwise be unreachable. */
- struct node *parent = read_node(conn, get_parent(name));
+ struct node *parent = read_node(conn, get_parent(name, name));
if (!parent) {
send_error(conn, EINVAL);
return 0;
@@ -1073,7 +1073,7 @@ static void do_rm(struct connection *conn, struct buffered_data *in)
if (!node) {
/* Didn't exist already? Fine, if parent exists. */
if (errno == ENOENT) {
- node = read_node(conn, get_parent(name));
+ node = read_node(conn, get_parent(in, name));
if (node) {
send_ack(conn, XS_RM);
return;
--
2.6.6
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-18 7:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 7:31 [PATCH v2 0/5] xenstore: fix memory leak of xenstored Juergen Gross
2016-07-18 7:31 ` [PATCH v2 1/5] xenstore: call each xenstored command function with temporary context Juergen Gross
2016-07-19 10:04 ` Wei Liu
2016-07-19 10:35 ` Ian Jackson
2016-07-18 7:31 ` Juergen Gross [this message]
2016-07-19 10:04 ` [PATCH v2 2/5] xenstore: add explicit memory context parameter to get_parent() Wei Liu
2016-07-19 10:37 ` Ian Jackson
2016-07-19 10:37 ` Ian Jackson
2016-07-18 7:31 ` [PATCH v2 3/5] xenstore: add explicit memory context parameter to read_node() Juergen Gross
2016-07-19 10:04 ` Wei Liu
2016-07-19 10:38 ` Ian Jackson
2016-07-18 7:31 ` [PATCH v2 4/5] xenstore: add explicit memory context parameter to get_node() Juergen Gross
2016-07-19 10:05 ` Wei Liu
2016-07-19 10:39 ` Ian Jackson
2016-07-18 7:31 ` [PATCH v2 5/5] xenstore: use temporary memory context for firing watches Juergen Gross
2016-07-19 10:23 ` Wei Liu
2016-07-19 10:40 ` Ian Jackson
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=1468827089-9054-3-git-send-email-jgross@suse.com \
--to=jgross@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).