From: Dan Carpenter <dan.carpenter@oracle.com>
To: Andrew Zhu Aday <andrew.aday@columbia.edu>
Cc: smatch@vger.kernel.org
Subject: Re: Tracking Implicit Dependencies
Date: Mon, 2 Oct 2017 16:24:28 +0300 [thread overview]
Message-ID: <20171002132428.yacilmryvixgz7kv@mwanda> (raw)
In-Reply-To: <20170929205028.czg2ebslgqs62xu3@mwanda>
Here are my thoughts. This project is actually very difficult...
The resources we're allocating are probably tied to a file or a process
and Smatch doesn't really track that. It just tracks parameters. My
idea is that the resources are probably stored in a struct so we could
track that "(struct foo)->bar" gets set by SYSC_one() and checked by
SYSC_two().
Some of the information about when structs are set is stored in
function_type_value(). But the problem is that it ignores too common
functions like you already found out. And then nothing is saving when
it's queried.
I've never tried this before so it might not work. And everything is
always more complicated than you'd imagine.
regards,
dan carpenter
next prev parent reply other threads:[~2017-10-02 13:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 5:37 Tracking Implicit Dependencies Andrew Zhu Aday
[not found] ` <CAHAAGFn5UmXp_EYC9H2Qjj-qTN+ks10Lt_46qZ-orQgX5Tu8kw@mail.gmail.com>
2017-09-29 19:23 ` Andrew Zhu Aday
2017-09-29 19:36 ` Andrew Zhu Aday
2017-09-29 19:45 ` Andrew Zhu Aday
2017-09-29 21:07 ` Dan Carpenter
2017-09-29 20:56 ` Dan Carpenter
2017-09-29 20:50 ` Dan Carpenter
2017-09-29 21:09 ` Dan Carpenter
2017-10-02 13:24 ` Dan Carpenter [this message]
2017-09-29 21:17 ` Dan Carpenter
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=20171002132428.yacilmryvixgz7kv@mwanda \
--to=dan.carpenter@oracle.com \
--cc=andrew.aday@columbia.edu \
--cc=smatch@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).