| commit | b949758eaf3dc4ff6f9868ebb842efbc0df44cb2 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Thu, 10 May 2012 18:44:58 +0000 (10 21:44 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Thu, 10 May 2012 18:44:58 +0000 (10 21:44 +0300) | ||
| tree | b79b8d20bfd9639c6656e39a0b59c2c0c2cb85cb | treesnapshot (tar.gz zip) |
| parent | c22264b3f2e05cc6704db1a65a4f743cf7731fe1 | commitdiff |
user_data: track user data that is returned to other functions
This isn't totally correct. I was trying to catch a specific bug where
you pass user data to a function and it does some math to it, and you get
user data back as the return value.
So the rule here is that if you are passing user data to a function that
sometimes returns user data then the returned data is user data. It
doesn't account for data that was received from the user inside the
function.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
This isn't totally correct. I was trying to catch a specific bug where
you pass user data to a function and it does some math to it, and you get
user data back as the return value.
So the rule here is that if you are passing user data to a function that
sometimes returns user data then the returned data is user data. It
doesn't account for data that was received from the user inside the
function.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| check_user_data.c | diffblobblamehistory | |
| smatch_db.c | diffblobblamehistory | |
| smatch_scripts/db/fill_db_return_info.pl | diffblobblamehistory | |
| smatch_scripts/db/return_info.schema | diffblobblamehistory |