| commit | ed4baf44f43a47ace4a632131dce14eeb9c1a0c0 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Mon, 13 Jun 2016 10:50:49 +0000 (13 13:50 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Mon, 13 Jun 2016 10:50:49 +0000 (13 13:50 +0300) | ||
| tree | 32d7cb50fc3693640da47ae7e39b7ddfed1f1c40 | treesnapshot (tar.gz zip) |
| parent | 80c35dc6904a55b444f6f9a4c2d79bd1529df04e | commitdiff |
db/kernel.return_fixes: hack around down_interruptible()
The problem here is that if you haven't rebuilt your database a few times
then smatch doesn't know what down_interruptible() returns and it breaks it
up into zero or anything. The problem is that check_locking says anything
is both locked and unlocked, and zero is unlocked. It gets confused and
prints a double unlock warning.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
The problem here is that if you haven't rebuilt your database a few times
then smatch doesn't know what down_interruptible() returns and it breaks it
up into zero or anything. The problem is that check_locking says anything
is both locked and unlocked, and zero is unlocked. It gets confused and
prints a double unlock warning.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_data/db/kernel.return_fixes | diffblobblamehistory |