From: Paul Bolle <pebolle@tiscali.nl>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/1] [RFC] kconfig: warn if an unknown symbol is selected
Date: Sat, 27 Sep 2014 00:08:29 +0200 [thread overview]
Message-ID: <1411769309.15241.37.camel@x220> (raw)
A select of an unknown symbol is basically treated as a nop and is
silently skipped. This is annoying if the selected symbol contains a
typo. It can also hide the fact that a treewide symbol cleanup was only
done partially.
There are also a few cases were this might have been done on purpose.
But that anti-pattern should be discouraged. Almost all select
statements point to a known and reachable symbol. So people will likely
assume that any selected symbol is actually set. Violating that
assumption might lead to (subtle) bugs.
So let's warn when we notice a select of a symbol that is not known in
the configuration we're creating.
Rfced-by: Paul Bolle <pebolle@tiscali.nl>
---
scripts/kconfig/conf.c | 41 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
diff --git a/scripts/kconfig/conf.c b/scripts/kconfig/conf.c
index fef75fc756f4..de8406287531 100644
--- a/scripts/kconfig/conf.c
+++ b/scripts/kconfig/conf.c
@@ -446,6 +446,45 @@ static void check_conf(struct menu *menu)
check_conf(child);
}
+static void check_selects(struct menu *menu)
+{
+ struct symbol *sym, *sel;
+ struct property *prop;
+
+ while (menu) {
+ sym = menu->sym;
+
+ if (sym && !sym_is_choice(sym) &&
+ sym->type != S_UNKNOWN &&
+ sym->flags & SYMBOL_WRITE) {
+ for_all_properties(sym, prop, P_SELECT) {
+ sel = prop->expr->left.sym;
+ if (sel->type == S_UNKNOWN &&
+ expr_calc_value(prop->visible.expr) != no) {
+ fprintf(stderr, "%s:%d:warning: ",
+ prop->file->name,
+ prop->lineno);
+ fprintf(stderr,
+ "'%s' selects unknown symbol '%s'\n",
+ sym->name,
+ sel->name);
+ }
+ }
+ }
+
+ if (menu->list) {
+ menu = menu->list;
+ } else if (menu->next) {
+ menu = menu->next;
+ } else while ((menu = menu->parent)) {
+ if (menu->next) {
+ menu = menu->next;
+ break;
+ }
+ }
+ }
+}
+
static struct option long_opts[] = {
{"oldaskconfig", no_argument, NULL, oldaskconfig},
{"oldconfig", no_argument, NULL, oldconfig},
@@ -681,6 +720,8 @@ int main(int ac, char **av)
break;
}
+ check_selects(rootmenu.list);
+
if (sync_kconfig) {
/* silentoldconfig is used during the build so we shall update autoconf.
* All other commands are only used to generate a config.
--
1.9.3
next reply other threads:[~2014-09-26 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 22:08 Paul Bolle [this message]
2014-09-29 14:41 ` Michal Marek
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=1411769309.15241.37.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yann.morin.1998@free.fr \
/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
Powered by JetHome