From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: jsperbeck@google.com
Subject: Re: selftests/powerpc: Add a test of SEGV error behaviour
Date: Thu, 18 Jan 2018 00:30:11 +1100 (AEDT) [thread overview]
Message-ID: <3zM7Hl70krz9t2l@ozlabs.org> (raw)
In-Reply-To: <20180102110324.31978-1-mpe@ellerman.id.au>
On Tue, 2018-01-02 at 11:03:24 UTC, Michael Ellerman wrote:
> Add a test case of the error code reported when we take a SEGV on a
> mapped but inaccessible area. We broke this recently.
>
> Based on a test case from John Sperbeck <jsperbeck@google.com>.
>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> Acked-by: John Sperbeck <jsperbeck@google.com>
Applied to powerpc next.
https://git.kernel.org/powerpc/c/6ed361586b323e576fd5536078fe9f
cheers
prev parent reply other threads:[~2018-01-17 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 11:03 [PATCH] selftests/powerpc: Add a test of SEGV error behaviour Michael Ellerman
2018-01-02 19:41 ` John Sperbeck
2018-01-03 6:14 ` Michael Ellerman
2018-01-17 13:30 ` Michael Ellerman [this message]
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=3zM7Hl70krz9t2l@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=jsperbeck@google.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).