From: Miles Chen Date: Tue, 2 Jun 2020 04:48:33 +0000 (-0700) Subject: mm/gup.c: further document vma_permits_fault() X-Git-Tag: microblaze-v5.10~696^2~71 X-Git-Url: http://git.monstr.eu/?a=commitdiff_plain;h=548b6a1e5520d5647e3d39c0aaf1f83ab27e250f;p=linux-2.6-microblaze.git mm/gup.c: further document vma_permits_fault() Describe the caller's responsibilities when passing FAULT_FLAG_ALLOW_RETRY. Link: http://lkml.kernel.org/r/1586915606.5647.5.camel@mtkswgap22 Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds --- diff --git a/mm/gup.c b/mm/gup.c index c3014669988b..1d84291543fd 100644 --- a/mm/gup.c +++ b/mm/gup.c @@ -1176,7 +1176,8 @@ static bool vma_permits_fault(struct vm_area_struct *vma, * @address: user address * @fault_flags:flags to pass down to handle_mm_fault() * @unlocked: did we unlock the mmap_sem while retrying, maybe NULL if caller - * does not allow retry + * does not allow retry. If NULL, the caller must guarantee + * that fault_flags does not contain FAULT_FLAG_ALLOW_RETRY. * * This is meant to be called in the specific scenario where for locking reasons * we try to access user memory in atomic context (within a pagefault_disable()