summaryrefslogtreecommitdiffstats
path: root/mm/kasan
diff options
context:
space:
mode:
authorPeter Xu <peterx@redhat.com>2020-05-13 17:50:41 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2020-05-14 10:00:35 -0700
commit475f4dfc021c5fde69f3b7d3287bde0a50477b05 (patch)
tree373f3598e3aab1c3067be1cc43714f0c440056ac /mm/kasan
parent65759097d804d2a9ad2b687db436319704ba7019 (diff)
downloadlinux-475f4dfc021c5fde69f3b7d3287bde0a50477b05.tar.gz
linux-475f4dfc021c5fde69f3b7d3287bde0a50477b05.tar.bz2
linux-475f4dfc021c5fde69f3b7d3287bde0a50477b05.zip
mm/gup: fix fixup_user_fault() on multiple retries
This part was overlooked when reworking the gup code on multiple retries. When we get the 2nd+ retry, we'll be with TRIED flag set. Current code will bail out on the 2nd retry because the !TRIED check will fail so the retry logic will be skipped. What's worse is that, it will also return zero which errornously hints the caller that the page is faulted in while it's not. The !TRIED flag check seems to not be needed even before the mutliple retries change because if we get a VM_FAULT_RETRY, it must be the 1st retry, and we should not have TRIED set for that. Fix it by removing the !TRIED check, at the meantime check against fatal signals properly before the page fault so we can still properly respond to the user killing the process during retries. Fixes: 4426e945df58 ("mm/gup: allow VM_FAULT_RETRY for multiple times") Reported-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Peter Xu <peterx@redhat.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Cc: Alex Williamson <alex.williamson@redhat.com> Cc: Brian Geffon <bgeffon@google.com> Link: http://lkml.kernel.org/r/20200502003523.8204-1-peterx@redhat.com Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/kasan')
0 files changed, 0 insertions, 0 deletions