linux-kernel - Re: [PATCH] Coccinelle: add atomic_as

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: <alpine.DEB.2.20.1708171346010.3748@hadrien>
Date:   Thu, 17 Aug 2017 13:50:08 +0200 (CEST)
From:   Julia Lawall <julia.lawall@...6.fr>
To:     Elena Reshetova <elena.reshetova@...el.com>
cc:     linux-kernel@...r.kernel.org, cocci@...teme.lip6.fr,
        Gilles Muller <Gilles.Muller@...6.fr>, nicolas.palix@...g.fr,
        mmarek@...e.com, keescook@...omium.org, ishkamiel@...il.com
Subject: Re: [PATCH] Coccinelle: add atomic_as_refcounter script

> +identifier fname =~ ".*free.*";
> +identifier fname2 =~ ".*destroy.*";
> +identifier fname3 =~ ".*del.*";
> +identifier fname4 =~ ".*queue_work.*";
> +identifier fname5 =~ ".*schedule_work.*";
> +identifier fname6 =~ ".*call_rcu.*";

Personally, I find the above regular expressions much easier to understand
than the merged version that Markus proposed.  But the performance issue is
only on whether to use regular expressions or not.  If you use regular
expressions, Coccinelle will not do some optimizations.  But once you
decide to use regular expressions, the performance hit is already taken -
for a good cause here, to my understanding.  So just put whatever you find
convenient, in terms of readability, precision, etc.  It seems that del is
not very precise, because it is a substring of multiple words with
different meanings.  Maybe it should be improved, or maybe one can just
live with the false positives (eg delay), if they actually are false
positives.

julia