linux-kernel - Re: [RFC PATCH v1] checkpatch: Handle FILE pointer type

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]

Date:   Thu, 1 Sep 2022 17:53:23 +0200
From:   Mickaël Salaün <mic@...ikod.net>
To:     Joe Perches <joe@...ches.com>, Andy Whitcroft <apw@...onical.com>
Cc:     Dwaipayan Ray <dwaipayanray1@...il.com>,
        Lukas Bulwahn <lukas.bulwahn@...il.com>,
        Shuah Khan <shuah@...nel.org>, linux-kernel@...r.kernel.org,
        linux-kselftest@...r.kernel.org
Subject: Re: [RFC PATCH v1] checkpatch: Handle FILE pointer type



On 01/09/2022 17:49, Joe Perches wrote:
> On Thu, 2022-09-01 at 16:59 +0200, Mickaël Salaün wrote:

[...]

>> +# our $typeKselftestHarnessTypedefs = qr{(?x:
>> +# 	FIXTURE_(?:DATA|VARIANT)\($Ident\)
>> +# )};
> 
> But not this.  Random userspace typedefs should likely
> be kept in some local version of checkpatch.
> 
> Or maybe add a command line option like --additional_typedefs=<file>.

This is part of the kselftest harness API. Could we take this into 
account for files under tools/testing/selftests ?

> 
>>   our $typeTypedefs = qr{(?x:
>>   	$typeC99Typedefs\b|
>>   	$typeOtherOSTypedefs\b|
>> -	$typeKernelTypedefs\b
>> +	$typeKernelTypedefs\b|
>> +	$typeStdioTypedefs\b
>>   )};
>