Masahiro Yamada bb222ceeb3 kconfig: remove string expansion in file_lookup()
There are two callers of file_lookup(), but there is no more reason
to expand the given path.

[1] zconf_initscan()
    This is used to open the first Kconfig.  sym_expand_string_value()
    has never been used in a useful way here; before opening the first
    Kconfig file, obviously there is no symbol to expand.  If you use
    expand_string_value() instead, environments in KBUILD_KCONFIG would
    be expanded, but I do not see practical benefits for that.

[2] zconf_nextfile()
    This is used to open the next file from 'source' statement.
    Symbols in the path like "arch/$SRCARCH/Kconfig" needed expanding,
    but it was replaced with the direct environment expansion.  The
    environment has already been expanded before the token is passed
    to the parser.

By the way, file_lookup() was already buggy; it expanded a given path,
but it used the path before expansion for look-up:
        if (!strcmp(name, file->name)) {

Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Reviewed-by: Ulf Magnusson <ulfalizer@gmail.com>
2018-05-29 03:28:58 +09:00
..
2018-03-28 14:30:41 +10:00
2017-03-28 16:16:52 +02:00
2018-05-03 01:17:44 +09:00
2017-11-17 17:45:29 -08:00
2018-04-03 15:51:22 -07:00
2018-03-26 02:01:18 +09:00
2018-02-02 00:21:47 +09:00
2011-08-31 16:12:17 +02:00
2012-06-27 12:44:29 -07:00
2018-04-04 16:01:43 -07:00
2018-05-29 03:28:58 +09:00
2017-11-17 17:45:29 -08:00
2017-11-14 18:25:40 -08:00
2017-11-17 17:45:29 -08:00
2018-02-06 18:32:47 -08:00
2017-11-17 17:45:29 -08:00
2017-11-17 17:45:29 -08:00
2018-04-04 16:43:47 -07:00
2014-08-20 16:03:45 +02:00