From: Dirk Gouders <dirk@gouders.net>
To: linux-kbuild@vger.kernel.org
Cc: Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] kconfig/menu.c: fix multiple references to expressions in menu_add_prop()
Date: Tue, 21 May 2013 14:36:28 +0200 [thread overview]
Message-ID: <giwqqsmrw3.fsf@karga.hank.lab> (raw)
In-Reply-To: <1369126451-11930-1-git-send-email-dirk@gouders.net> (Dirk Gouders's message of "Tue, 21 May 2013 10:54:11 +0200")
CCing the original author of the code (commit 7ad1227818f09 "kconfig:
fix undesirable side effect of adding "visible" menu attribute").
Dirk
Dirk Gouders <dirk@gouders.net> writes:
> menu_add_prop() applies upper menus' visibilities to actual prompts
> by AND-ing the prompts visibilities with the upper menus ones.
>
> This creates a further reference to the menu's visibilities and when
> the expression reduction functions do their work, they may remove or
> modify expressions that have multiple references, thus causing
> unpredictable side-effects.
>
> The following example Kconfig constructs a case where this causes
> problems: a menu and a prompt which's visibilities depend on the same
> symbol. When invoking mconf with this Kconfig and pressing "Z" we
> see a problem caused by a free'd expression still referenced by the
> menu's visibility:
>
> ------------------------------------------------------------------------
> mainmenu "Kconfig Testing Configuration"
>
> config VISIBLE
> def_bool n
>
> config Placeholder
> bool "Place holder"
>
> menu "Invisible"
> visible if VISIBLE
>
> config TEST_VAR
> bool "Test option" if VISIBLE
>
> endmenu
> ------------------------------------------------------------------------
>
> This patch fixes this problem by creating copies of the menu's
> visibility expressions before AND-ing them with the prompt's one.
>
> Signed-off-by: Dirk Gouders <dirk@gouders.net>
> ---
> scripts/kconfig/menu.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/kconfig/menu.c b/scripts/kconfig/menu.c
> index b5c7d90..567939c 100644
> --- a/scripts/kconfig/menu.c
> +++ b/scripts/kconfig/menu.c
> @@ -143,14 +143,25 @@ struct property *menu_add_prop(enum prop_type type, char *prompt, struct expr *e
>
> /* Apply all upper menus' visibilities to actual prompts. */
> if(type == P_PROMPT) {
> + struct expr *dup_expr;
> struct menu *menu = current_entry;
>
> while ((menu = menu->parent) != NULL) {
> if (!menu->visibility)
> continue;
> + /*
> + * Do not add a reference to the
> + * menu's visibility expression but
> + * use a copy of it. Otherwise the
> + * expression reduction functions
> + * will modify expressions that have
> + * multiple references which can
> + * cause unwanted side-effects.
> + */
> + dup_expr = expr_copy(menu->visibility);
> +
> prop->visible.expr
> - = expr_alloc_and(prop->visible.expr,
> - menu->visibility);
> + = expr_alloc_and(prop->visible.expr, dup_expr);
> }
> }
next prev parent reply other threads:[~2013-05-21 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 8:54 [PATCH] kconfig/menu.c: fix multiple references to expressions in menu_add_prop() Dirk Gouders
2013-05-21 12:36 ` Dirk Gouders [this message]
2013-05-23 8:28 ` Yann E. MORIN
2013-05-23 10:25 ` Dirk Gouders
2013-05-29 21:58 ` Yann E. MORIN
2013-05-30 3:59 ` Dirk Gouders
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=giwqqsmrw3.fsf@karga.hank.lab \
--to=dirk@gouders.net \
--cc=jbeulich@suse.com \
--cc=linux-kbuild@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox