| commit | 78dad190e88c9983b3c0f729c9d61dabaf8fe0d3 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Wed, 7 Jan 2015 07:02:41 +0000 (7 10:02 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Wed, 7 Jan 2015 07:02:41 +0000 (7 10:02 +0300) | ||
| tree | dd8cb995af3cdd0bc6c63af7d3e4e87d14ca40df | treesnapshot (tar.gz zip) |
| parent | 63b0907254782a29f0ce970125ee6e3f4ff355ae | commitdiff |
db: it's not a condition return if we know it's true
Say we have a function call "validate_arch_id(201201);" and we know that
201201 means the function returns true, then we shouldn't handle that as
a condition return which returns 0-1, but as a known return of 1.
Reported-by: Josef 'Jeff' Sipek <jeffpc@josefsipek.net>
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Say we have a function call "validate_arch_id(201201);" and we know that
201201 means the function returns true, then we shouldn't handle that as
a condition return which returns 0-1, but as a known return of 1.
Reported-by: Josef 'Jeff' Sipek <jeffpc@josefsipek.net>
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_db.c | diffblobblamehistory |