Skip to content

Commit

Permalink
kconfig: don't crash on NULL expressions in expr_eq()
Browse files Browse the repository at this point in the history
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 <[email protected]>
Signed-off-by: Masahiro Yamada <[email protected]>
  • Loading branch information
tchebb authored and masahir0y committed Dec 17, 2019
1 parent fd2ab2f commit 272a721
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions scripts/kconfig/expr.c
Original file line number Diff line number Diff line change
Expand Up @@ -254,6 +254,13 @@ 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) {
Expand Down

0 comments on commit 272a721

Please sign in to comment.