diff options
| author | Brenda Streiff <brenda.streiff@ni.com> | 2022-01-28 16:01:28 -0600 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-02-23 11:58:42 +0100 |
| commit | 7d1c79a1cd16c3b14effa88a7d0e454e3caec697 (patch) | |
| tree | ba0220192d35994d7f261f2ceb9ffd243b371fb8 | |
| parent | b90eab91a2a232dcc7861c2c9a119fd5551837e0 (diff) | |
| download | linux-stable-7d1c79a1cd16c3b14effa88a7d0e454e3caec697.tar.gz linux-stable-7d1c79a1cd16c3b14effa88a7d0e454e3caec697.tar.bz2 linux-stable-7d1c79a1cd16c3b14effa88a7d0e454e3caec697.zip | |
kconfig: let 'shell' return enough output for deep path names
[ Upstream commit 8a4c5b2a6d8ea079fa36034e8167de87ab6f8880 ]
The 'shell' built-in only returns the first 256 bytes of the command's
output. In some cases, 'shell' is used to return a path; by bumping up
the buffer size to 4096 this lets us capture up to PATH_MAX.
The specific case where I ran into this was due to commit 1e860048c53e
("gcc-plugins: simplify GCC plugin-dev capability test"). After this
change, we now use `$(shell,$(CC) -print-file-name=plugin)` to return
a path; if the gcc path is particularly long, then the path ends up
truncated at the 256 byte mark, which makes the HAVE_GCC_PLUGINS
depends test always fail.
Signed-off-by: Brenda Streiff <brenda.streiff@ni.com>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
| -rw-r--r-- | scripts/kconfig/preprocess.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/scripts/kconfig/preprocess.c b/scripts/kconfig/preprocess.c index 389814b02d06..8c7e51a6273c 100644 --- a/scripts/kconfig/preprocess.c +++ b/scripts/kconfig/preprocess.c @@ -138,7 +138,7 @@ static char *do_lineno(int argc, char *argv[]) static char *do_shell(int argc, char *argv[]) { FILE *p; - char buf[256]; + char buf[4096]; char *cmd; size_t nread; int i; |