| commit | 5b6677cbaa61aa657daf5a4824acdcf4e6758b33 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Wed, 18 Jan 2017 14:09:09 +0000 (18 17:09 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Wed, 18 Jan 2017 14:09:09 +0000 (18 17:09 +0300) | ||
| tree | 5404dbab9ea6cec1991baad091163d34dbb522d2 | treesnapshot (tar.gz zip) |
| parent | 59ad5f85f291bcfd5f34eaffe0bef9e4de28b36e | commitdiff |
user_data2: don't set the function itself to user_data
This doesn't affect real life, but I was looking at the debug output and
noticed this mistake. Say the user can control the return value of a
function, but we don't care because we don't store the return, in that
case, program was setting the function itself to user_data.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
This doesn't affect real life, but I was looking at the debug output and
noticed this mistake. Say the user can control the return value of a
function, but we don't care because we don't store the return, in that
case, program was setting the function itself to user_data.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| check_user_data2.c | diffblobblamehistory |