From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.linuxfoundation.org ([140.211.169.12]:39664 "EHLO
	mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751505AbbDZKtF (ORCPT
	<rfc822;stable@vger.kernel.org>); Sun, 26 Apr 2015 06:49:05 -0400
Date: Sun, 26 Apr 2015 12:49:02 +0200
From: Greg KH <gregkh@linuxfoundation.org>
To: Sheng Yong <shengyong1@huawei.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2 0/3][request for stable 3.10 inclusion] vm: make stack
 guard page errors return VM_FAULT_SIGSEGV rather than SIGBUS
Message-ID: <20150426104902.GA5003@kroah.com>
References: <1425035663-9349-1-git-send-email-shengyong1@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1425035663-9349-1-git-send-email-shengyong1@huawei.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Fri, Feb 27, 2015 at 11:14:20AM +0000, Sheng Yong wrote:
> Hi, Greg,
> 
> V2:
> Backport commit 7fb08eca ("x86: mm: move mmap_sem unlock from
> mm_fault_error() to caller)" to solve lock problem on x86.
> 
> V1:
> The commit 88b5d12 ("mm: propagate error from stack expansion even for
> guard page") for 3.10-stable makes the testcase get "bus error", while
> it had "segmentation fault" in older kernels.
> 
> ===== testcase =====
> int main(void)
> {
> 	main();
> 	return 0;
> }
> ====================
> 
> These 2 patches fix it by adding a VM_FAULT_SIGSEGV in all architecture
> fault handlers.
> 
> [PATCH 1/3] is asjusted to ignore un-supported arch and driver in 3.10.
> And some files are separated or renamed in newer kernel, so [PATCH 1/3]
> is also adjusted to add the VM_FAULT_SIGSEGV handling in the original
> files in 3.10.
> 
> thanks,
> Sheng

I think I've now queued these up properly, but can you test to verify I
got it correct?

thanks,

greg k-h