linux-kernel - More benefits from higher level structures for coccicheck scripts?

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

Message-ID: <1fab8d2f-20e5-4e92-afb3-53167fecab54@web.de>
Date: Fri, 21 Feb 2025 11:11:09 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: cocci@...ia.fr
Cc: LKML <linux-kernel@...r.kernel.org>, kernel-janitors@...r.kernel.org
Subject: More benefits from higher level structures for coccicheck scripts?

Hello,

Various source code was assigned to functions (or function-like macros).
Common functionality is stored at selected places.
Thus there is a desire to increase the corresponding usage.

Some scripts were constructed also according to the means of the semantic
patch language.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/dev-tools/coccinelle.rst?h=v6.14-rc3#n71

It can be seen that some of these SmPL scripts share also program structures.

* Operation modes need to be determined.

* Special source code items should be detected somehow.

* Data output should be provided.

Would you be looking for the support of higher level structures for
coccicheck scripts?

Is there a need for placeholders (or variables) which could be filled from
other advanced information sources so that selected data processing
will eventually not be mapped to separate SmPL script files to achieve more
desirable transformations?

Regards,
Markus