linux-kernel - Re: [PATCH 2/3] checkpatch: recognize __chkp_no_side_effects(

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: <2362285823b62590148255214d53997ab128ea37.camel@perches.com>
Date: Sun, 26 Oct 2025 09:48:42 -0700
From: Joe Perches <joe@...ches.com>
To: Jim Cromie <jim.cromie@...il.com>, linux-kernel@...r.kernel.org
Cc: akpm@...uxfoundation.org, Andy Whitcroft <apw@...onical.com>, Dwaipayan
 Ray	 <dwaipayanray1@...il.com>, Lukas Bulwahn <lukas.bulwahn@...il.com>
Subject: Re: [PATCH 2/3] checkpatch: recognize __chkp_no_side_effects(_var)
 hint macro

On Sat, 2025-10-25 at 15:15 -0600, Jim Cromie wrote:
> Teach checkpatch --strict to allow an author to suppress specific
> var-reuse complaints:

It seems to me that annotating source code to silence checkpatch
isn't a great idea.

If it is a great idea, maybe a general CHECKPATCH_ON/OFF(type)
mechanism might be better than specific controls.