All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: "Jérémy Lefaure" <jeremy.lefaure@netatmo.com>,
	cocci@inria.fr, kernel-janitors@vger.kernel.org
Cc: Julia Lawall <julia.lawall@inria.fr>,
	Nicolas Palix <nicolas.palix@imag.fr>
Subject: Re: [cocci] [PATCH v3] coccinelle: Extend address test from ifaddr to every test expression
Date: Thu, 16 Jun 2022 08:32:41 +0200	[thread overview]
Message-ID: <6aef3ee4-d934-daff-7145-73ac563d2fb4@web.de> (raw)
In-Reply-To: <AS8PR03MB76033CF2848D03651D6E189093A69@AS8PR03MB7603.eurprd03.prod.outlook.com>


> The test of an expression's address does not necessarily represent the
> whole condition, it may only be a part of it. Also, an expression's
> address is likely to be non-zero in every test expression, not only in
> if statements.
>
> This change aims at detecting an address test in more complex conditions
> for every test expression.
>
> Signed-off-by: Jérémy Lefaure <jeremy.lefaure@netatmo.com>
> ---
> v2 -> v3: Apply Julia's suggestion to have a more generic solution + adapt commit message and file
>           name to this new solution.
> v1 -> v2: Moved disjunction on the condition itself instead of being on the
>           if statements.
>
>  scripts/coccinelle/misc/{ifaddr.cocci => test_addr.cocci} | 4 +---


It can be determined that the proposed approach for the detection of
questionable source code places is incomplete (also because of the current
development status for the Coccinelle software).
Thus I suggest to reconsider the usage of the word “every” for the patch message
once more.
Will further adjustments become helpful for desired source code analyses
and corresponding transformations?

Regards,
Markus


  parent reply	other threads:[~2022-06-16  6:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 11:18 [PATCH v3] coccinelle: Extend address test from ifaddr to every test expression Jérémy LEFAURE
2022-06-10 11:18 ` [cocci] " Jérémy LEFAURE
2022-06-10 17:36 ` Markus Elfring
2022-06-10 17:42   ` Julia Lawall
2022-06-10 17:42     ` [cocci] " Julia Lawall
2022-06-10 18:05     ` [cocci] " Markus Elfring
2022-06-13 16:25   ` [cocci] [PATCH v3] " Jérémy LEFAURE
2022-06-13 16:25     ` Jérémy LEFAURE
2022-06-13 18:11     ` [cocci] " Julia Lawall
2022-06-13 18:11       ` Julia Lawall
2022-06-13 19:08     ` [cocci] " Markus Elfring
2022-06-16  6:32 ` Markus Elfring [this message]
2022-06-21 16:10   ` Jérémy LEFAURE
2022-06-21 17:16     ` [cocci] " Markus Elfring
2022-06-23 16:17       ` Jérémy LEFAURE
2022-06-23 19:35         ` Markus Elfring
2022-06-21 19:42     ` [cocci] [PATCH v3] " Julia Lawall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6aef3ee4-d934-daff-7145-73ac563d2fb4@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@inria.fr \
    --cc=jeremy.lefaure@netatmo.com \
    --cc=julia.lawall@inria.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=nicolas.palix@imag.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.