diff options
| author | Ian Jackson <Ian.Jackson@eu.citrix.com> | 2011-01-11 19:31:41 +0000 |
|---|---|---|
| committer | Ian Jackson <Ian.Jackson@eu.citrix.com> | 2011-01-11 19:31:41 +0000 |
| commit | 54fbaf446bb350aff4dd5c4b0f44557186dd7d31 (patch) | |
| tree | 935bc0f929a867e75ad01a6d21cc97ea8f1c02da /tools/libxl/libxlu_cfg_i.h | |
| parent | 3e58e5d9c1fdc16dee74b891403f30e987965877 (diff) | |
| download | xen-54fbaf446bb350aff4dd5c4b0f44557186dd7d31.tar.gz xen-54fbaf446bb350aff4dd5c4b0f44557186dd7d31.tar.bz2 xen-54fbaf446bb350aff4dd5c4b0f44557186dd7d31.zip | |
libxl: config parser: print warning for apparent arbitrary python
The characters - + . ( ) : are not legal in xl config files but are
valid Python and use of at least one of them is almost essential for
writing arbitrary Python in the config file.
So if we see one of these during lexing, note it, and then after the
parse is complete if it failed we print a special extra warning.
Currently this warning refers to the nonexistent wiki page
http://wiki.xen.org/xenwiki/PythonInXlConfig
which will have to be written (and/or given a better name) before the
actual 4.1 release.
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
Diffstat (limited to 'tools/libxl/libxlu_cfg_i.h')
| -rw-r--r-- | tools/libxl/libxlu_cfg_i.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/tools/libxl/libxlu_cfg_i.h b/tools/libxl/libxlu_cfg_i.h index f6b241cf09..88d2a02811 100644 --- a/tools/libxl/libxlu_cfg_i.h +++ b/tools/libxl/libxlu_cfg_i.h @@ -16,6 +16,8 @@ char *xlu__cfgl_dequote(CfgParseContext*, const char *src); void xlu__cfg_yyerror(YYLTYPE *locp, CfgParseContext*, char const *msg); void xlu__cfgl_lexicalerror(CfgParseContext*, char const *msg); +void xlu__cfgl_likely_python(CfgParseContext *ctx); + /* Why oh why does bison not declare this in its autogenerated .h ? */ |