| commit | b1e87c2c41f6bcb76e6e37bf7e5152c75c5090c1 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Tue, 25 Nov 2014 13:44:10 +0000 (25 16:44 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Tue, 25 Nov 2014 13:44:10 +0000 (25 16:44 +0300) | ||
| tree | c17df15a885de6aa7a12e3623602b32fdac468dc | treesnapshot (tar.gz zip) |
| parent | 02d472da24d8a8121d6e7b09c10e2d4c4f339b14 | commitdiff |
db: create a clear_user_data.sh script
The sad fact is that the user data tainting sucks a bit. To do it properly
then you basically need to recreate smatch_extra.c and
smatch_param_limit/filter/add.c but only for tracking user controlled data
instead of tracking all data. It's a lot of work. Every couple weeks I
just blow away the user data information from the database and start fresh.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
The sad fact is that the user data tainting sucks a bit. To do it properly
then you basically need to recreate smatch_extra.c and
smatch_param_limit/filter/add.c but only for tracking user controlled data
instead of tracking all data. It's a lot of work. Every couple weeks I
just blow away the user data information from the database and start fresh.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_data/db/clear_user_data.sh | [new file with mode: 0755] | blob |