Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp3765676imm; Mon, 2 Jul 2018 05:18:23 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcC/LOe2T4/ZFjfoPb7wLykTlR9AsiH/50rR6JNyPsc7T6xlwtN5BS33gYqNM3cW+LJNVuS X-Received: by 2002:a63:5204:: with SMTP id g4-v6mr1640664pgb.274.1530533903407; Mon, 02 Jul 2018 05:18:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530533903; cv=none; d=google.com; s=arc-20160816; b=OyLHz+d0+vu3E+2gPSBqqbWVX6wE1J3mPCD0ppLXuiCpH2JUce89HaBQLPF5OzgKVB 2BLu/muzAildNerC9w2gBbhe/NoUcMGteZkY79Jgg+R7jLStwjTc+MifLbv5xHCnrxOS azx+NfPCIQbmQM6ea7zuH7zmjNuJ22TQwuLnTM94X3IhCQNb3yugFEkqIpKIU/7myRk3 tUudac3IcQalBkyH4g6Y9vzahXHO90EO0xP8JoZKcel5ZJp72JkmS0/XfyKTNhBrz+xy a2ZP+3RnD0w7SarliFBEiQC3QAZOM5kamQ8D4mIzDG1n4nh3TACueWjTobOjY4XOEjCq wB/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=A1xPcOSReaG9r4OuJ+mhhdPYRJb1znw7FFfsI4ZI79I=; b=WEsYzSTQyTr8v6YUv4tPptyNmh03fLpw4HTmEEUvGQ+T+QupOk+RW/aPjJzD3/pbbK r9SumXedlIt6STWVXUhiUPhdZsNABz1DzOVCE1AX0YqiURmQ2Xynj77a3p2pe5VpsrYy wZys5NqWI2d43ZdQCGuVmQPAmBFQgoUzpakGnZ60gHRIbrCew3fJCHXY+1VUkF/8VbQX wSioGJSse9ijlIs3oNilrwvkU5/gzrjnxWBu2IEbb386UQsq9wYVuUusRKUuneo0ZWpF xBYtmoG6iwaNsAIJGf5TuwednXvDwRVyqV5zFx2V4/hHGNPyvFWMHgeRM+dporOAwlt3 RySw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n6-v6si5801077pgt.268.2018.07.02.05.18.08; Mon, 02 Jul 2018 05:18:23 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752558AbeGBMPe (ORCPT + 99 others); Mon, 2 Jul 2018 08:15:34 -0400 Received: from mx2.suse.de ([195.135.220.15]:56710 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751761AbeGBMPb (ORCPT ); Mon, 2 Jul 2018 08:15:31 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 8D935AD06; Mon, 2 Jul 2018 12:15:29 +0000 (UTC) Date: Mon, 2 Jul 2018 14:15:28 +0200 From: Michal Hocko To: Laurent Dufour Cc: Yang Shi , willy@infradead.org, akpm@linux-foundation.org, peterz@infradead.org, mingo@redhat.com, acme@kernel.org, alexander.shishkin@linux.intel.com, jolsa@redhat.com, namhyung@kernel.org, tglx@linutronix.de, hpa@zytor.com, linux-mm@kvack.org, x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC v3 PATCH 5/5] x86: check VM_DEAD flag in page fault Message-ID: <20180702121528.GM19043@dhcp22.suse.cz> References: <1530311985-31251-1-git-send-email-yang.shi@linux.alibaba.com> <1530311985-31251-6-git-send-email-yang.shi@linux.alibaba.com> <84eba553-2e0b-1a90-d543-6b22c1b3c5f8@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <84eba553-2e0b-1a90-d543-6b22c1b3c5f8@linux.vnet.ibm.com> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 02-07-18 10:45:03, Laurent Dufour wrote: > On 30/06/2018 00:39, Yang Shi wrote: > > Check VM_DEAD flag of vma in page fault handler, if it is set, trigger > > SIGSEGV. > > > > Cc: Michal Hocko > > Cc: Thomas Gleixner > > Cc: Ingo Molnar > > Cc: "H. Peter Anvin" > > Signed-off-by: Yang Shi > > --- > > arch/x86/mm/fault.c | 4 ++++ > > 1 file changed, 4 insertions(+) > > > > diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c > > index 9a84a0d..3fd2da5 100644 > > --- a/arch/x86/mm/fault.c > > +++ b/arch/x86/mm/fault.c > > @@ -1357,6 +1357,10 @@ static inline bool smap_violation(int error_code, struct pt_regs *regs) > > bad_area(regs, error_code, address); > > return; > > } > > + if (unlikely(vma->vm_flags & VM_DEAD)) { > > + bad_area(regs, error_code, address); > > + return; > > + } > > This will have to be done for all the supported architectures, what about doing > this check in handle_mm_fault() and return VM_FAULT_SIGSEGV ? We already do have a model for that. Have a look at MMF_UNSTABLE. -- Michal Hocko SUSE Labs