aboutsummaryrefslogtreecommitdiffstats
path: root/firmware/korg
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2011-05-04 21:30:28 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2011-05-04 21:30:28 -0700
commita1fde08c74e90accd62d4cfdbf580d2ede938fe7 (patch)
treebdf58078fd37484729e350acb066dc1b1fa890ee /firmware/korg
parent5895198c56d131cc696556a45f7ff0ea99ac297b (diff)
downloadkernel_samsung_tuna-a1fde08c74e90accd62d4cfdbf580d2ede938fe7.zip
kernel_samsung_tuna-a1fde08c74e90accd62d4cfdbf580d2ede938fe7.tar.gz
kernel_samsung_tuna-a1fde08c74e90accd62d4cfdbf580d2ede938fe7.tar.bz2
VM: skip the stack guard page lookup in get_user_pages only for mlock
The logic in __get_user_pages() used to skip the stack guard page lookup whenever the caller wasn't interested in seeing what the actual page was. But Michel Lespinasse points out that there are cases where we don't care about the physical page itself (so 'pages' may be NULL), but do want to make sure a page is mapped into the virtual address space. So using the existence of the "pages" array as an indication of whether to look up the guard page or not isn't actually so great, and we really should just use the FOLL_MLOCK bit. But because that bit was only set for the VM_LOCKED case (and not all vma's necessarily have it, even for mlock()), we couldn't do that originally. Fix that by moving the VM_LOCKED check deeper into the call-chain, which actually simplifies many things. Now mlock() gets simpler, and we can also check for FOLL_MLOCK in __get_user_pages() and the code ends up much more straightforward. Reported-and-reviewed-by: Michel Lespinasse <walken@google.com> Cc: stable@kernel.org Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'firmware/korg')
0 files changed, 0 insertions, 0 deletions