From: Ram Pai <linuxram@us.ibm.com>
To: Li Wang <liwang@redhat.com>
Cc: Cyril Hrubis <chrubis@suse.cz>, Jan Stancek <jstancek@redhat.com>,
Michael Ellerman <mpe@ellerman.id.au>,
ltp@lists.linux.it, linux-mm@kvack.org,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [bug?] Access was denied by memory protection keys in execute-only address
Date: Fri, 23 Mar 2018 17:44:40 -0700 [thread overview]
Message-ID: <20180324004440.GA5887@ram.oc3035372033.ibm.com> (raw)
In-Reply-To: <CAEemH2c4p7FqYs9L9X0SyjUvg5Z3pfwsokurJmzq+=y1h2OwbA@mail.gmail.com>
On Fri, Mar 23, 2018 at 05:27:06PM +0800, Li Wang wrote:
> On Thu, Mar 22, 2018 at 3:09 PM, Ram Pai <[1]linuxram@us.ibm.com> wrote:
>
> On Wed, Mar 21, 2018 at 02:53:00PM +0800, Li Wang wrote:
> > On Wed, Mar 21, 2018 at 5:58 AM, Ram Pai
> <[1][2]linuxram@us.ibm.com> wrote:
> > that why not disable the pkey_execute_disable_supported on p8
.snip..
> machine?
>
> It turns out to be a testcase bug. On Big endian powerpc ABI, function
> ptrs are basically pointers to function descriptors. The testcase
> copies functions which results in function descriptors getting copied.
> You have to apply the following patch to your test case for it to
> operate as intended. Thanks to Michael Ellermen for helping me out.
> Otherwise I would be scratching my head for ever.
>
> Thanks for the explanation, I learned something new about this. :)
>
> And the worth to say, seems the patch only works on powerpc arch,
> others(x86_64, etc)
> that does not works well, so a simple workaround is to isolate the code
> changes
> to powerpc system?
yes. this code has to be made applicable to powerpc Big-endian code
only. The powerpc little-endian code remains unchanged.
RP
prev parent reply other threads:[~2018-03-24 0:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEemH2f0LDqyR5AmUYv17OuBc5-UycckDPWgk46XU_ghQo4diw@mail.gmail.com>
2018-03-08 12:19 ` [bug?] Access was denied by memory protection keys in execute-only address Michael Ellerman
2018-03-08 16:45 ` Ram Pai
2018-03-09 3:43 ` Li Wang
2018-03-09 5:50 ` Ram Pai
2018-03-20 21:58 ` Ram Pai
2018-03-21 6:53 ` Li Wang
2018-03-22 7:09 ` Ram Pai
2018-03-23 9:27 ` Li Wang
2018-03-24 0:44 ` Ram Pai [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=20180324004440.GA5887@ram.oc3035372033.ibm.com \
--to=linuxram@us.ibm.com \
--cc=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--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).