Move fiddling with rip.x_max and rip.y_max out of the vstat mutex.
Apparently, fiddling with them in there "strongly implies" to Coverity that vstatlock needs to be held to access them, and it's good form to have the lock held for the least span possible.
parent
64919b72
No related branches found
No related tags found
Please register or sign in to comment