| commit | de69db75c0fc7ca2dd478e951819ad3642f1180f | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Wed, 16 Dec 2020 13:16:32 +0000 (16 16:16 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Wed, 16 Dec 2020 13:16:32 +0000 (16 16:16 +0300) | ||
| tree | 8fb0f6c3936f39c57fba333bf23e4af9713f67d2 | treesnapshot (tar.gz zip) |
| parent | e465a8870d683247bb6b23f3bcfb8391f29b6c79 | commitdiff |
points_to_user_data: Make copy_from_user() set point to user data
Say we have a pointer "p" and we copy user data to it then it points to
user data. And if we do p++ then that's points to user data as well.
If "p" is a struct then that's fine because the struct members because
those are handled in smatch_kernel_user_data.c already and nothing changes.
It's only when we start using p + 1 that this makes a difference.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Say we have a pointer "p" and we copy user data to it then it points to
user data. And if we do p++ then that's points to user data as well.
If "p" is a struct then that's fine because the struct members because
those are handled in smatch_kernel_user_data.c already and nothing changes.
It's only when we start using p + 1 that this makes a difference.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_points_to_user_data.c | diffblobblamehistory |