linux-kernel - Re: [PATCH 03/10] kconfig: refactor conf_write

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]

Message-ID: <boris.20211105133811@codesynthesis.com>
Date:   Fri, 5 Nov 2021 13:40:54 +0200
From:   Boris Kolpackov <boris@...esynthesis.com>
To:     Masahiro Yamada <masahiroy@...nel.org>
Cc:     Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 03/10] kconfig: refactor conf_write_symbol()

Masahiro Yamada <masahiroy@...nel.org> writes:

> Without this patch, there are some functions that start with double
> underscores.
> 
> For example,
> 
>   __expr_eliminate_eq() in scripts/kconfig/expr.c
>   __expand_string()  in scripts/kconfig/preprocess.c
> 
> Are they problematic as well?

Yes, they could be potentially problematic. Identifiers that start
with double underscores or with a single underscore followed by an
uppercase letter are reserved for use by the C implementation (for
example, as a pre-defined macro).