From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Searching for pass-through functions
Date: Sun, 05 Oct 2014 18:38:40 +0200 [thread overview]
Message-ID: <54317410.6040605@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1410051729480.2022@localhost6.localdomain6>
> I'm not sure what is the goal of your semantic patch.
The shown pattern should not be a patch at this time. ;-)
I try to find functions by this approach that do not perform validation for a
specific input parameter usually because this parameter will be forwarded as the
return value.
> For example are you only interested in pointers?
No. - But I imagine that pointers will be specified more often in corresponding
function signatures than integral data types.
> Another thing that could be helpful is to check if there exists the
> pattern you are looking for, before checking whether it is found on all
> execution paths. You can use the same rule you have, but with exists in
> the header, and then have a second rule that checks all paths and depends
> on the first one.
Would you like to show your fine-tuning suggestion in the affected SmPL script?
> Also, since you just want to find returns, but don't care about what
> happens in between, you can use arguments like --no-loops and --no-gotos.
Will it matter if the relevant return statement will be executed within a loop
or is also marked with a jump label?
Can the five issues on which I stumbled during the source code analysis be fixed
anyhow (eventually without the addtion of "--no-?" command options)?
Regards,
Markus
next prev parent reply other threads:[~2014-10-05 16:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 17:49 [Cocci] Searching for pass-through functions SF Markus Elfring
2014-10-04 19:17 ` Julia Lawall
2014-10-04 20:22 ` SF Markus Elfring
2014-10-04 21:32 ` Julia Lawall
2014-10-05 6:48 ` SF Markus Elfring
2014-10-05 9:39 ` Julia Lawall
2014-10-05 13:15 ` SF Markus Elfring
2014-10-05 11:45 ` SF Markus Elfring
2014-10-05 11:48 ` Julia Lawall
2014-10-05 12:15 ` SF Markus Elfring
2014-10-05 15:33 ` Julia Lawall
2014-10-05 16:38 ` SF Markus Elfring [this message]
2014-10-05 16:42 ` Julia Lawall
2014-10-05 16:55 ` SF Markus Elfring
2014-10-05 17:01 ` Julia Lawall
2014-10-05 17:09 ` SF Markus Elfring
2014-10-05 18:37 ` SF Markus Elfring
2014-10-08 11:40 ` SF Markus Elfring
2014-10-08 11:51 ` Julia Lawall
2014-10-08 12:01 ` SF Markus Elfring
2014-10-08 12:08 ` Julia Lawall
2014-10-08 12:20 ` SF Markus Elfring
2014-10-08 12:48 ` Julia Lawall
2014-10-08 13:01 ` SF Markus Elfring
2014-10-08 18:05 ` SF Markus Elfring
2014-10-09 5:37 ` Julia Lawall
2014-10-07 19:39 ` SF Markus Elfring
2014-10-07 19:44 ` Julia Lawall
2014-10-07 20:20 ` SF Markus Elfring
2014-10-07 20:26 ` 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=54317410.6040605@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.