diff options
| author | Janosch Frank | 2018-08-16 10:02:31 +0200 |
|---|---|---|
| committer | Janosch Frank | 2018-09-12 14:46:37 +0200 |
| commit | 1843abd03250115af6cec0892683e70cf2297c25 (patch) | |
| tree | b764158970ec421902e4ad739adac90a3dd42adb /arch/s390/scripts | |
| parent | KVM: s390: Properly lock mm context allow_gmap_hpage_1m setting (diff) | |
| download | kernel-qcow2-linux-1843abd03250115af6cec0892683e70cf2297c25.tar.gz kernel-qcow2-linux-1843abd03250115af6cec0892683e70cf2297c25.tar.xz kernel-qcow2-linux-1843abd03250115af6cec0892683e70cf2297c25.zip | |
s390/mm: Check for valid vma before zapping in gmap_discard
Userspace could have munmapped the area before doing unmapping from
the gmap. This would leave us with a valid vmaddr, but an invalid vma
from which we would try to zap memory.
Let's check before using the vma.
Fixes: 1e133ab296f3 ("s390/mm: split arch/s390/mm/pgtable.c")
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
Message-Id: <20180816082432.78828-1-frankja@linux.ibm.com>
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Diffstat (limited to 'arch/s390/scripts')
0 files changed, 0 insertions, 0 deletions