summaryrefslogtreecommitdiffstats
path: root/drivers/mmc
diff options
context:
space:
mode:
authorMasahiro Yamada <yamada.masahiro@socionext.com>2018-12-11 20:00:45 +0900
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-01-26 09:32:39 +0100
commit461991104dcb0f3e601128e707833ea8cf1ceb46 (patch)
treec860b5474ae4b2d8b0472778576e5f2f5ded2f9b /drivers/mmc
parentba8efcdc5779d549eda39e48d243522e37da9032 (diff)
downloadlinux-stable-461991104dcb0f3e601128e707833ea8cf1ceb46.tar.gz
linux-stable-461991104dcb0f3e601128e707833ea8cf1ceb46.tar.bz2
linux-stable-461991104dcb0f3e601128e707833ea8cf1ceb46.zip
kconfig: fix memory leak when EOF is encountered in quotation
[ Upstream commit fbac5977d81cb2b2b7e37b11c459055d9585273c ] An unterminated string literal followed by new line is passed to the parser (with "multi-line strings not supported" warning shown), then handled properly there. On the other hand, an unterminated string literal at end of file is never passed to the parser, then results in memory leak. [Test Code] ----------(Kconfig begin)---------- source "Kconfig.inc" config A bool "a" -----------(Kconfig end)----------- --------(Kconfig.inc begin)-------- config B bool "b\No new line at end of file ---------(Kconfig.inc end)--------- [Summary from Valgrind] Before the fix: LEAK SUMMARY: definitely lost: 16 bytes in 1 blocks ... After the fix: LEAK SUMMARY: definitely lost: 0 bytes in 0 blocks ... Eliminate the memory leak path by handling this case. Of course, such a Kconfig file is wrong already, so I will add an error message later. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/mmc')
0 files changed, 0 insertions, 0 deletions