linux-kernel - Re: [kconfig] results of some syntactical checks

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 18 Jul 2013 14:17:56 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Martin Walch <walch.martin@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [kconfig] results of some syntactical checks

On Wed, 2013-07-17 at 15:07 +0200, Martin Walch wrote:
> All this can be avoided by quoting values, i. e.
> 
> 	range "8260" "8272"
> 
> and
> 
>         default "4711"

Documentation/kbuild/kconfig-language.txt even states
    Constant symbols are always surrounded by single or double quotes.

But apparently the parser doesn't care. All "range" digits are unquoted,
and most "default" digits are unquoted.

> Also, avoiding integers (and hex values) as symbol names looks like a 
> reasonable idea.

I was actually surprised that these were allowed, and only discovered
that when my local script generated a few false positives. But, anyhow,
in practice those symbol names seem to work just fine.


Paul Bolle

--
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/