Powered by Linux
Re: Tracking Implicit Dependencies — Semantic Matching Tool

Re: Tracking Implicit Dependencies

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Fri, Sep 29, 2017 at 03:36:16PM -0400, Andrew Zhu Aday wrote:
> Also, when parsing a function definition, why does smatch only follow
> some internal function calls? For example, in the syscall
> `get_mempolicy` in ``mm/mempolicy.c`,
> it will follow the call to `copy_nodes_to_user`, but will not follow
> `do_get_mempolicy`.
> Is there a way I can make it follow all internal function calls?

I'm not totally sure I understand the question.  It follows everything.

I suspect that what you're looking is that copy_nodes_to_user() is
parsed inline and get_mempolicy() isn't.  In smatch_flow.c look at the
places which reference __inline_fn and you'll see the rules for this.
Basically inlines don't nest, it has to be shorter than 20 lines long
and have a max of 10 statements.

There is the smatch_db.sqlite file normal cross function analysis and
another sqlite DB in ram for handling inline functions.

dan carpenter
To unsubscribe from this list: send the line "unsubscribe smatch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux