linux-kernel - [PATCH 0/2] kconfig: warn of unhandled characters in statements

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri,  3 Jul 2015 14:46:37 +0200
From:	Andreas Ruprecht <andreas.ruprecht@....de>
To:	Ulf Magnusson <ulfalizer.lkml@...il.com>
Cc:	Paul Bolle <pebolle@...cali.nl>,
	Valentin Rothberg <valentinrothberg@...il.com>,
	rafael.j.wysocki@...el.com, <linux-kbuild@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>,
	hengelein Stefan <stefan.hengelein@....de>,
	linux@...inikbrodowski.net, Michal Marek <mmarek@...e.cz>,
	Andreas Ruprecht <andreas.ruprecht@....de>
Subject: [PATCH 0/2] kconfig: warn of unhandled characters in statements

This patchset changes the lexer file to emit a warning if any unhandled
characters are found in the input. So far, Kconfig options like

 +config FOO
    bool
    [...]

(note the wrong '+'!) were parsed without a warning. As simply adding a
warning for '.' produces lots of warnings as occasionally '---help---'
is used instead of 'help' (and thus '-' is recognized as an unhandled
character), we need to handle the former separately.

Andreas Ruprecht (2):
  kconfig: also warn of unhandled characters in statements
  kconfig: Regenerate shipped zconf.lex.c file

 scripts/kconfig/zconf.l             |  11 +-
 scripts/kconfig/zconf.lex.c_shipped | 453 +++++++++++++++++++++++++-----------
 2 files changed, 322 insertions(+), 142 deletions(-)

-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/