From: Justin Mitchell <jumitche@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Cc: Steve Dickson <SteveD@RedHat.com>
Subject: [PATCH v2 2/7] nfs-utils: Make config includes relative to current config
Date: Thu, 03 May 2018 17:48:05 +0100 [thread overview]
Message-ID: <1525366085.7550.20.camel@redhat.com> (raw)
In-Reply-To: <1525365943.7550.18.camel@redhat.com>
When including additional config files with the include directive
make relative paths be relative to the current config file instead
of to the process's cwd.
Signed-off-by: Justin Mitchell <jumitche@redhat.com>
---
support/nfs/conffile.c | 76 +++++++++++++++++++++++++++++++++++++++++---------
1 file changed, 63 insertions(+), 13 deletions(-)
diff --git a/support/nfs/conffile.c b/support/nfs/conffile.c
index 28e29b7..95dda99 100644
--- a/support/nfs/conffile.c
+++ b/support/nfs/conffile.c
@@ -49,6 +49,7 @@
#include <errno.h>
#include <err.h>
#include <syslog.h>
+#include <libgen.h>
#include "conffile.h"
#include "xlog.h"
@@ -60,7 +61,7 @@ static char * conf_readfile(const char *path);
static int conf_set(int , const char *, const char *, const char *,
const char *, int , int );
static void conf_parse(int trans, char *buf,
- char **section, char **subsection);
+ char **section, char **subsection, const char *filename);
struct conf_trans {
TAILQ_ENTRY (conf_trans) link;
@@ -206,12 +207,49 @@ conf_set_now(const char *section, const char *arg, const char *tag,
return 0;
}
+/* Attempt to construct a relative path to the new file */
+static char *
+relative_path(const char *oldfile, const char *newfile)
+{
+ char *tmpcopy = NULL;
+ char *dir = NULL;
+ char *relpath = NULL;
+ size_t pathlen;
+
+ if (!newfile)
+ return strdup(oldfile);
+
+ if (newfile[0] == '/')
+ return strdup(newfile);
+
+ tmpcopy = strdup(oldfile);
+ if (!tmpcopy)
+ goto mem_err;
+
+ dir = dirname(tmpcopy);
+
+ pathlen = strlen(dir) + strlen(newfile) + 2;
+ relpath = calloc(1, pathlen);
+ if (!relpath)
+ goto mem_err;
+
+ snprintf(relpath, pathlen, "%s/%s", dir, newfile);
+
+ free(tmpcopy);
+ return relpath;
+mem_err:
+ if (tmpcopy)
+ free(tmpcopy);
+ return NULL;
+}
+
+
/*
* Parse the line LINE of SZ bytes. Skip Comments, recognize section
* headers and feed tag-value pairs into our configuration database.
*/
static void
-conf_parse_line(int trans, char *line, int lineno, char **section, char **subsection)
+conf_parse_line(int trans, char *line, const char *filename, int lineno, char **section, char **subsection)
{
char *val, *ptr;
@@ -366,27 +404,34 @@ conf_parse_line(int trans, char *line, int lineno, char **section, char **subsec
if (strcasecmp(line, "include")==0) {
/* load and parse subordinate config files */
- char * subconf = conf_readfile(val);
+ char *inc_section = NULL;
+ char *inc_subsection = NULL;
+ char *relpath = relative_path(filename, val);
+ char *subconf = conf_readfile(relpath);
if (subconf == NULL) {
- xlog_warn("config file error: line %d: "
- "error loading included config", lineno);
+ xlog_warn("%s:%d: error loading included config",
+ filename, lineno);
+ if (relpath)
+ free(relpath);
return;
}
/* copy the section data so the included file can inherit it
* without accidentally changing it for us */
- char * inc_section = NULL;
- char * inc_subsection = NULL;
if (*section != NULL) {
inc_section = strdup(*section);
if (*subsection != NULL)
inc_subsection = strdup(*subsection);
}
- conf_parse(trans, subconf, &inc_section, &inc_subsection);
+ conf_parse(trans, subconf, &inc_section, &inc_subsection, relpath);
- if (inc_section) free(inc_section);
- if (inc_subsection) free(inc_subsection);
+ if (inc_section)
+ free(inc_section);
+ if (inc_subsection)
+ free(inc_subsection);
+ if (relpath)
+ free(relpath);
free(subconf);
} else {
/* XXX Perhaps should we not ignore errors? */
@@ -396,7 +441,7 @@ conf_parse_line(int trans, char *line, int lineno, char **section, char **subsec
/* Parse the mapped configuration file. */
static void
-conf_parse(int trans, char *buf, char **section, char **subsection)
+conf_parse(int trans, char *buf, char **section, char **subsection, const char *filename)
{
char *cp = buf;
char *bufend = NULL;
@@ -413,7 +458,7 @@ conf_parse(int trans, char *buf, char **section, char **subsection)
else {
*cp = '\0';
lineno++;
- conf_parse_line(trans, line, lineno, section, subsection);
+ conf_parse_line(trans, line, filename, lineno, section, subsection);
line = cp + 1;
}
}
@@ -434,6 +479,11 @@ static char *
conf_readfile(const char *path)
{
struct stat sb;
+ if (!path) {
+ xlog_err("conf_readfile: no path given");
+ return NULL;
+ }
+
if ((stat (path, &sb) == 0) || (errno != ENOENT)) {
char *new_conf_addr = NULL;
size_t sz = sb.st_size;
@@ -508,7 +558,7 @@ conf_load_file(const char *conf_file)
/* Parse config contents into the transaction queue */
char *section = NULL;
char *subsection = NULL;
- conf_parse(trans, conf_data, §ion, &subsection);
+ conf_parse(trans, conf_data, §ion, &subsection, conf_file);
if (section) free(section);
if (subsection) free(subsection);
free(conf_data);
--
1.8.3.1
next prev parent reply other threads:[~2018-05-03 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 16:45 [PATCH v2 0/7] nfs-utils: nfsconf cli tool and code tests Justin Mitchell
2018-05-03 16:47 ` [PATCH v2 1/7] nfs-utils: Fix minor memory leaks Justin Mitchell
2018-05-03 16:48 ` Justin Mitchell [this message]
2018-05-03 16:48 ` [PATCH v2 3/7] nfs-utils: Use config file name in error messages Justin Mitchell
2018-05-03 16:49 ` [PATCH v2 4/7] nfs-utils: Indicate if config file was missing Justin Mitchell
2018-05-03 16:50 ` [PATCH v2 5/7] nfs-utils: tidy up output of conf_report Justin Mitchell
2018-05-03 16:50 ` [PATCH v2 6/7] nfs-utils: Add nfsconftool cli Justin Mitchell
2018-05-03 16:51 ` [PATCH v2 7/7] nfs-utils: use nfsconftool cli to test library function Justin Mitchell
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=1525366085.7550.20.camel@redhat.com \
--to=jumitche@redhat.com \
--cc=SteveD@RedHat.com \
--cc=linux-nfs@vger.kernel.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).