linux-kernel - Re: [PATCH] checkpatch: simplify the output of --list-types

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: <20170905113734.5afafc62@endymion>
Date:   Tue, 5 Sep 2017 11:37:34 +0200
From:   Jean Delvare <jdelvare@...e.de>
To:     Joe Perches <joe@...ches.com>
Cc:     Andy Whitcroft <apw@...onical.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] checkpatch: simplify the output of --list-types

On Mon, 04 Sep 2017 08:48:36 -0700, Joe Perches wrote:
> On Mon, 2017-09-04 at 10:08 +0200, Jean Delvare wrote:
> > Drop the header and numbering of types. This format was confusing as
> > it suggested one could pass the number instead of the type name,
> > however it did not actually work, and numbering wasn't stable anyway.  
> 
> <shrug>  If it makes you happy.
> 
> I suppose a bigger improvement would be to detail
> the purpose of each type.

That would be great indeed, however this would require a completely
different approach, as I can't think of a way to automatically extract
this information by just parsing the script.

> Most are fairly obvious, some like MEMSET are
> a bit obscure.
> 
> Another defect:
> 
> The list also includes types that are commented out.

This could be considered a feature: if they were not listed, the user
would have no idea that they can be commented out.

OTOH I'm not sure why some tests are commented out in the first place,
it doesn't make much sense to me. Either they serve a purpose and they
should be enabled, or there is some kind of issue with them and they
should be either fixed or deleted altogether.

-- 
Jean Delvare
SUSE L3 Support