[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <2f42719235f9250ed10209982543f99f4fd41d61.1575879069.git.tommyhebb@gmail.com>
Date: Mon, 9 Dec 2019 00:19:17 -0800
From: Thomas Hebb <tommyhebb@...il.com>
To: linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org
Cc: Thomas Hebb <tommyhebb@...il.com>,
Masahiro Yamada <yamada.masahiro@...ionext.com>
Subject: [PATCH 2/4] kconfig: don't crash on NULL expressions in expr_eq()
NULL expressions are taken to always be true, as implemented by the
expr_is_yes() macro and by several other functions in expr.c. As such,
they ought to be valid inputs to expr_eq(), which compares two
expressions.
Signed-off-by: Thomas Hebb <tommyhebb@...il.com>
---
scripts/kconfig/expr.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/scripts/kconfig/expr.c b/scripts/kconfig/expr.c
index 77ffff3a053c..8284444cc3fa 100644
--- a/scripts/kconfig/expr.c
+++ b/scripts/kconfig/expr.c
@@ -254,6 +254,11 @@ static int expr_eq(struct expr *e1, struct expr *e2)
{
int res, old_count;
+ /* A NULL expr is taken to be yes, but there's also a different way to
+ * represent yes. expr_is_yes() checks for either representation. */
+ if (!e1 || !e2)
+ return expr_is_yes(e1) && expr_is_yes(e2);
+
if (e1->type != e2->type)
return 0;
switch (e1->type) {
--
2.24.0
Powered by blists - more mailing lists