user_data: reading from an array doesn't necessarily give user data
commitdceb945cfa0153e5ad6adb1916f70014aa5a186e
authorDan Carpenter <dan.carpenter@oracle.com>
Wed, 7 Mar 2018 09:55:51 +0000 (7 12:55 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Wed, 7 Mar 2018 09:55:51 +0000 (7 12:55 +0300)
tree997a09c8abc6765a9901c6041687530e658366ea
parent1050a135e82dc57f902b3bc14b956073f8630002
user_data: reading from an array doesn't necessarily give user data

Say you have a user defined offset into a kernel controlled array.  Smatch
was saying that because the offset was user controlled and the result was
unknown that meant that the result was an entirely unknown user controlled
value.

This silences that.  It's a big hammer approach, but it probably doesn't
silence any real bugs.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
check_user_data2.c