All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Sun, 26 Apr 2015 12:49:02 +0200	[thread overview]
Message-ID: <20150426104902.GA5003@kroah.com> (raw)
In-Reply-To: <1425035663-9349-1-git-send-email-shengyong1@huawei.com>

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

           reply	other threads:[~2015-04-26 10:49 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1425035663-9349-1-git-send-email-shengyong1@huawei.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150426104902.GA5003@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=shengyong1@huawei.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.