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]
Date:   Sat, 31 Aug 2019 19:26:41 +0200
From:   Markus Elfring <Markus.Elfring@....de>
To:     Denis Efremov <efremov@...ux.com>, Joe Perches <joe@...ches.com>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Anton Altaparmakov <anton@...era.com>,
        Andy Whitcroft <apw@...onical.com>,
        Boris Ostrovsky <boris.ostrovsky@...cle.com>,
        Boris Pismenny <borisp@...lanox.com>,
        "Darrick J. Wong" <darrick.wong@...cle.com>,
        "David S. Miller" <davem@...emloft.net>,
        Dennis Dalessandro <dennis.dalessandro@...el.com>,
        Dmitry Torokhov <dmitry.torokhov@...il.com>,
        dri-devel@...ts.freedesktop.org,
        Inaky Perez-Gonzalez <inaky.perez-gonzalez@...el.com>,
        Jürgen Groß <jgross@...e.com>,
        Leon Romanovsky <leon@...nel.org>,
        linux-arm-msm@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-ntfs-dev@...ts.sourceforge.net, linux-rdma@...r.kernel.org,
        linux-wimax@...el.com, linux-xfs@...r.kernel.org,
        Mike Marciniszyn <mike.marciniszyn@...el.com>,
        netdev@...r.kernel.org,
        Pali Rohár <pali.rohar@...il.com>,
        Rob Clark <robdclark@...il.com>,
        Saeed Mahameed <saeedm@...lanox.com>,
        Sean Paul <sean@...rly.run>,
        Alexander Viro <viro@...iv.linux.org.uk>,
        xen-devel@...ts.xenproject.org, Enrico Weigelt <lkml@...ux.net>
Subject: Re: [PATCH v3 01/11] checkpatch: check for nested (un)?likely() calls

>>>>> +# nested likely/unlikely calls
>>>>> +        if ($line =~ /\b(?:(?:un)?likely)\s*\(\s*!?\s*(IS_ERR(?:_OR_NULL|_VALUE)?|WARN)/) {
>>>>> +            WARN("LIKELY_MISUSE",
…
>> \b(?:un)?likely\s*
>
> This pair of brackets is required to match "unlikely"
> and it's optional in order to match "likely".

I agree also to this view if you refer to the shortened regular expression here.
But I got an other development opinion for an extra pair of non-capturing parentheses
at the front (from the version which you suggested).

Regards,
Markus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ