* Chris Wright (chrisw@xxxxxxxx) wrote:
* Darren Hart (dvhltc@xxxxxxxxxx) wrote:
The were a couple long standing (since at least 2.4.21) superfluous variables and two unnecessary assignments in do_mlock(). The intent of the resulting code is also more obvious.
Tested on a 4 way x86 box running a simple mlock test program. No problems detected.
Did you test with multiple page ranges, and locking subsets of vmas?
Seems that splitting could cause a problem since you now sample vm_end
before and after fixup, where the vma could be changed in the middle.
Actually I think it winds up being fine since we don't do merging with
mlock. But why not? Patch below remedies that.