mm/mempolicy: Allow lookup_node() to handle fatal signal
authorPeter Xu <peterx@redhat.com>
Wed, 8 Apr 2020 01:40:09 +0000 (21:40 -0400)
committerLinus Torvalds <torvalds@linux-foundation.org>
Wed, 8 Apr 2020 02:34:31 +0000 (19:34 -0700)
commitba841078cd0557b43b59c63f5c048b12168f0db2
tree3697b4a407d713c5aca73827a2d34574865508e8
parent63bef48fd6c9d3f1ba4f0e23b4da1e007db6a3c0
mm/mempolicy: Allow lookup_node() to handle fatal signal

lookup_node() uses gup to pin the page and get node information.  It
checks against ret>=0 assuming the page will be filled in.  However it's
also possible that gup will return zero, for example, when the thread is
quickly killed with a fatal signal.  Teach lookup_node() to gracefully
return an error -EFAULT if it happens.

Meanwhile, initialize "page" to NULL to avoid potential risk of
exploiting the pointer.

Fixes: 4426e945df58 ("mm/gup: allow VM_FAULT_RETRY for multiple times")
Reported-by: syzbot+693dc11fcb53120b5559@syzkaller.appspotmail.com
Signed-off-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
mm/mempolicy.c