Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161923AbdD0Py1 (ORCPT ); Thu, 27 Apr 2017 11:54:27 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:47595 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1033864AbdD0Pxe (ORCPT ); Thu, 27 Apr 2017 11:53:34 -0400 From: Laurent Dufour To: paulmck@linux.vnet.ibm.com, peterz@infradead.org, akpm@linux-foundation.org, kirill@shutemov.name, ak@linux.intel.com, mhocko@kernel.org, dave@stgolabs.net, jack@suse.cz Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, haren@linux.vnet.ibm.com, khandual@linux.vnet.ibm.com, npiggin@gmail.com, bsingharora@gmail.com Subject: [RFC v3 15/17] mm/spf: Add check on the VMA's flags Date: Thu, 27 Apr 2017 17:52:54 +0200 X-Mailer: git-send-email 2.7.4 In-Reply-To: <1493308376-23851-1-git-send-email-ldufour@linux.vnet.ibm.com> References: <1493308376-23851-1-git-send-email-ldufour@linux.vnet.ibm.com> X-TM-AS-GCONF: 00 x-cbid: 17042715-0012-0000-0000-0000051A061E X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17042715-0013-0000-0000-0000183D9BC4 Message-Id: <1493308376-23851-16-git-send-email-ldufour@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-04-27_14:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1704270259 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1469 Lines: 46 When handling speculative page fault we should check for the VMA's access permission as it is done in handle_mm_fault() or access_error in x86's fault handler. Signed-off-by: Laurent Dufour --- mm/memory.c | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/mm/memory.c b/mm/memory.c index 3b28de5838c7..4d9c6331ada1 100644 --- a/mm/memory.c +++ b/mm/memory.c @@ -3756,6 +3756,30 @@ int handle_speculative_fault(struct mm_struct *mm, unsigned long address, if (address < vma->vm_start || vma->vm_end <= address) goto unlock; + /* XXX Could we handle huge page here ? */ + if (unlikely(is_vm_hugetlb_page(vma))) + goto unlock; + + /* + * The three following checks are copied from access_error from + * arch/x86/mm/fault.c + * XXX they may not be applicable to all architectures + */ + if (!arch_vma_access_permitted(vma, flags & FAULT_FLAG_WRITE, + flags & FAULT_FLAG_INSTRUCTION, + flags & FAULT_FLAG_REMOTE)) + goto unlock; + + /* This is one is required to check that the VMA has write access set */ + if (flags & FAULT_FLAG_WRITE) { + if (unlikely(!(vma->vm_flags & VM_WRITE))) + goto unlock; + } else { + /* XXX This may not be required */ + if (unlikely(!(vma->vm_flags & (VM_READ | VM_EXEC | VM_WRITE)))) + goto unlock; + } + /* * We need to re-validate the VMA after checking the bounds, otherwise * we might have a false positive on the bounds. -- 2.7.4