All of lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Improving size determinations with SmPL
Date: Thu, 17 Aug 2017 17:57:08 +0200	[thread overview]
Message-ID: <a0bda451-ef87-2317-2abc-62b1bd59e386@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1708171721280.3748@hadrien>

> ... when any should be ...>

I am unsure if I interpret your suggestion correctly.


@replacement@
identifier action, var, work;
type T, X;
@@
 T work(...)
 {
 <... ... when any ...>
 X* var;
 <... ... when any ...>
 var = action(...,
              sizeof(
-                    X
+                    *var
                    ),
              ...
             )
 <... ... when any ...>
 }


elfring at Sonne:~/Projekte/Linux/next-patched> git checkout next-20170803 && spatch.opt ~/Projekte/Coccinelle/janitor/safer_size_determination2.cocci fs/pstore/ram.c
?
minus: parse error: 
  File "/home/elfring/Projekte/Coccinelle/janitor/safer_size_determination2.cocci", line 7, column 6, charpos = 80
  around = '...',
  whole content =  <... ... when any ...>



> You request that the sizeof appear on every execution path.

I hope not. - I would like to express that this operator can appear for
a parameter of a function call.

Does the variable declaration ?struct persistent_ram_zone *tmp_prz, *prz_next;?
in the function ?ramoops_pstore_read? trigger challenges for the attempted
source code transformation?

Regards,
Markus

  reply	other threads:[~2017-08-17 15:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17 15:18 [Cocci] Improving size determinations with SmPL SF Markus Elfring
2017-08-17 15:22 ` Julia Lawall
2017-08-17 15:57   ` SF Markus Elfring [this message]
2017-08-17 16:00     ` Julia Lawall
2017-08-17 16:11       ` SF Markus Elfring
     [not found]   ` <alpine.DEB.2.20.1708171818300.3748@hadrien>
2017-08-17 16:50     ` SF Markus Elfring
2017-08-18  8:00       ` SF Markus Elfring
2017-08-18  8:49         ` Julia Lawall
2017-08-18  9:15           ` SF Markus Elfring

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=a0bda451-ef87-2317-2abc-62b1bd59e386@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=cocci@systeme.lip6.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.