mm/mempolicy: Allow lookup_node() to handle fatal signal

mainline inclusion
from mainline-v5.7-rc1
commit ba841078
category: bugfix
bugzilla: 47439
CVE: NA
---------------------------

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: 4426e945 ("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>
 Conflicts:
	mm/mempolicy.c
Signed-off-by: Xiongfeng Wang <wangxiongfeng2@huawei.com>
Reviewed-by: Jing Xiangfeng <jingxiangfeng@huawei.com>
Reviewed-by: Kefeng  Wang <wangkefeng.wang@huawei.com>
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Signed-off-by: Cheng Jian <cj.chengjian@huawei.com>