linux-kernel - Re: [PATCH 0/7] Support for automatic checkpatch running in the kernel

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

Message-ID: <CAGXu5j+j0TZ+QUMf09eifTwOwmgA=3AbA3e2PJQehKF61hMcRA@mail.gmail.com>
Date:   Thu, 16 Nov 2017 14:57:33 -0800
From:   Kees Cook <keescook@...omium.org>
To:     Knut Omang <knut.omang@...cle.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Åsmund Østvold <asmund.ostvold@...cle.com>,
        Håkon Bugge <haakon.bugge@...cle.com>,
        John Haxby <john.haxby@...cle.com>, linux-doc@...r.kernel.org,
        linux-kbuild <linux-kbuild@...r.kernel.org>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Mickaël Salaün <mic@...ikod.net>,
        Joe Perches <joe@...ches.com>
Subject: Re: [PATCH 0/7] Support for automatic checkpatch running in the kernel

On Thu, Nov 16, 2017 at 9:01 AM, Knut Omang <knut.omang@...cle.com> wrote:
> The most important checkpatch feature added is the --ignore-cfg feature, which
> takes a file argument and parses that file according to this minimal language:
>
>        # comments
>        line_len <n>
>        except checkpatch_type [files ...]
>        pervasive checkpatch_type1 [checkpatch_type2 ...]
>
> With "make P=2" checkpatch is called with "--file" and "--ignore_cfg
> checkpatch.cfg" which causes it to look for a file named 'checkpatch.cfg' in the
> same directory as the source file. If that file exists, checkpatch will be run
> with an implicit --strict and with the @ignore list expanded with content from
> the configuration file.  If it does not exist, make will simply silently ignore
> the file.

Will these configurations be cascading? (For example, all of net/ uses
a different comment style, so having that recorded in a single file
would be nice.)


-- 
Kees Cook
Pixel Security