From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xenproject.org
Cc: Juergen Gross <jgross@suse.com>, Wei Liu <wl@xen.org>,
Anthony PERARD <anthony.perard@citrix.com>
Subject: [PATCH v2 3/3] tools/xl: rework p9 config parsing
Date: Wed, 22 Mar 2023 08:34:53 +0100 [thread overview]
Message-ID: <20230322073453.7853-4-jgross@suse.com> (raw)
In-Reply-To: <20230322073453.7853-1-jgross@suse.com>
Rework the config parsing of a p9 device to use the
split_string_into_pair() function instead of open coding it.
Signed-off-by: Juergen Gross <jgross@suse.com>
---
V2:
- add libxl_string_list_dispose() call (Jason Andryuk)
---
tools/xl/xl_parse.c | 74 ++++++++++++++++++++++-----------------------
1 file changed, 37 insertions(+), 37 deletions(-)
diff --git a/tools/xl/xl_parse.c b/tools/xl/xl_parse.c
index 09cabd2732..1f6f47daf4 100644
--- a/tools/xl/xl_parse.c
+++ b/tools/xl/xl_parse.c
@@ -2180,54 +2180,54 @@ void parse_config_data(const char *config_source,
if (!xlu_cfg_get_list(config, "p9", &p9devs, 0, 0)) {
libxl_device_p9 *p9;
- char *security_model = NULL;
- char *path = NULL;
- char *tag = NULL;
- char *backend = NULL;
- char *p, *p2, *buf2;
d_config->num_p9s = 0;
d_config->p9s = NULL;
while ((buf = xlu_cfg_get_listitem (p9devs, d_config->num_p9s)) != NULL) {
+ libxl_string_list pairs;
+ int len;
+
p9 = ARRAY_EXTEND_INIT(d_config->p9s,
d_config->num_p9s,
libxl_device_p9_init);
libxl_device_p9_init(p9);
- buf2 = strdup(buf);
- p = strtok(buf2, ",");
- if(p) {
- do {
- while(*p == ' ')
- ++p;
- if ((p2 = strchr(p, '=')) == NULL)
- break;
- *p2 = '\0';
- if (!strcmp(p, "security_model")) {
- security_model = strdup(p2 + 1);
- } else if(!strcmp(p, "path")) {
- path = strdup(p2 + 1);
- } else if(!strcmp(p, "tag")) {
- tag = strdup(p2 + 1);
- } else if(!strcmp(p, "backend")) {
- backend = strdup(p2 + 1);
- } else {
- fprintf(stderr, "Unknown string `%s' in 9pfs spec\n", p);
- exit(1);
- }
- } while ((p = strtok(NULL, ",")) != NULL);
- }
- if (!path || !security_model || !tag) {
- fprintf(stderr, "9pfs spec missing required field!\n");
- exit(1);
+ split_string_into_string_list(buf, ",", &pairs);
+ len = libxl_string_list_length(&pairs);
+ for (i = 0; i < len; i++) {
+ char *key, *value;
+ int rc;
+
+ rc = split_string_into_pair(pairs[i], '=', &key, &value,
+ isspace);
+ if (rc != 0) {
+ fprintf(stderr, "failed to parse 9pfs configuration: %s",
+ pairs[i]);
+ exit(1);
+ }
+
+ if (!strcmp(key, "security_model")) {
+ replace_string(&p9->security_model, value);
+ } else if (!strcmp(key, "path")) {
+ replace_string(&p9->path, value);
+ } else if (!strcmp(key, "tag")) {
+ replace_string(&p9->tag, value);
+ } else if (!strcmp(key, "backend")) {
+ replace_string(&p9->backend_domname, value);
+ } else {
+ fprintf(stderr, "Unknown 9pfs parameter '%s'\n", key);
+ exit(1);
+ }
+ free(key);
+ free(value);
}
- free(buf2);
- replace_string(&p9->tag, tag);
- replace_string(&p9->security_model, security_model);
- replace_string(&p9->path, path);
- if (backend)
- replace_string(&p9->backend_domname, backend);
+ libxl_string_list_dispose(&pairs);
+
+ if (!p9->path || !p9->security_model || !p9->tag) {
+ fprintf(stderr, "9pfs spec missing required field!\n");
+ exit(1);
+ }
}
}
--
2.35.3
next prev parent reply other threads:[~2023-03-22 7:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 7:34 [PATCH v2 0/3] tools/xl: small cleanup of parsing code Juergen Gross
2023-03-22 7:34 ` [PATCH v2 1/3] tools/xl: allow split_string_into_pair() to trim values Juergen Gross
2023-03-22 7:34 ` [PATCH v2 2/3] tools/xl: make split_string_into_pair() more usable Juergen Gross
2023-03-22 12:29 ` Jason Andryuk
2023-03-22 17:28 ` Anthony PERARD
2023-03-22 7:34 ` Juergen Gross [this message]
2023-03-22 12:32 ` [PATCH v2 3/3] tools/xl: rework p9 config parsing Jason Andryuk
2023-03-22 17:29 ` Anthony PERARD
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=20230322073453.7853-4-jgross@suse.com \
--to=jgross@suse.com \
--cc=anthony.perard@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.