linux-kernel - [PATCH v1 0/3] Regarding using 'bool' appropriately

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-next>] [day] [month] [year] [list]

Date:   Sat,  4 Mar 2023 12:19:29 +0800
From:   Wei Wang <wei.w.wang@...el.com>
To:     arnd@...db.de, akpm@...ux-foundation.org, keescook@...omium.org,
        herbert@...dor.apana.org.au, josh@...htriplett.org,
        jani.nikula@...el.com, corbet@....net, jgg@...lanox.com,
        dmatlack@...gle.com, mizhang@...gle.com, pbonzini@...hat.com,
        seanjc@...gle.com
Cc:     linux-kernel@...r.kernel.org, Wei Wang <wei.w.wang@...el.com>
Subject: [PATCH v1 0/3] Regarding using 'bool' appropriately

When I'm working on patch 3 to change WARN/WARN_ON to use bool for
__ret_warn_on according to the documentation in CodingStyle about using
'bool', compiler reports an error from tpm2_key_encode(), and the root
cause is that it names a variable 'bool' which conficts with the data
type name 'bool'. So fix it and add a rule in CodingStyle to avoid such
naming that causes confusion. This is also the reason that the three
patches are grouped into one patchset.

Wei Wang (3):
  security: keys: don't use data type as variable name
  Documentation/CodingStyle: do not use data type names as variable
    names
  bug: use bool for __ret_warn_on in WARN/WARN_ON

 Documentation/process/coding-style.rst    |  3 +++
 include/asm-generic/bug.h                 | 12 ++++++------
 security/keys/trusted-keys/trusted_tpm2.c |  5 +++--
 tools/include/asm/bug.h                   | 10 +++++-----
 4 files changed, 17 insertions(+), 13 deletions(-)

-- 
2.27.0