| commit | 27ce87220809efcb78a73e19d76403b8fff9f4b2 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Tue, 28 Jan 2014 22:45:02 +0000 (29 01:45 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Tue, 28 Jan 2014 22:45:02 +0000 (29 01:45 +0300) | ||
| tree | bcc02ac8de65ecde24d4130e03c3eea9259a089f | treesnapshot (tar.gz zip) |
| parent | b519854712d97716aabf19f302c961fdf613ee25 | commitdiff |
capped: trace variable capping inside function calls
A lot of code calls to functions like is_valid(x). If we can put a hard
limit on what valid values are that gets tracked in smatch_param_limit.c
and friends. But we should also track if the code checks against an
upper bound, even if we don't know what the upper bound is exactly.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
A lot of code calls to functions like is_valid(x). If we can put a hard
limit on what valid values are that gets tracked in smatch_param_limit.c
and friends. But we should also track if the code checks against an
upper bound, even if we don't know what the upper bound is exactly.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch.h | diffblobblamehistory | |
| smatch_capped.c | diffblobblamehistory | |
| smatch_comparison.c | diffblobblamehistory |