From: Michael Ellerman <mpe@ellerman.id.au>
To: Li Wang <liwang@redhat.com>, linuxram@us.ibm.com
Cc: Jan Stancek <jstancek@redhat.com>,
ltp@lists.linux.it, linux-mm@kvack.org,
linuxppc-dev@lists.ozlabs.orglinuxppc-dev@lists.ozlabs.org
Subject: Re: [bug?] Access was denied by memory protection keys in execute-only address
Date: Thu, 08 Mar 2018 23:19:12 +1100 [thread overview]
Message-ID: <871sguep4v.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <CAEemH2f0LDqyR5AmUYv17OuBc5-UycckDPWgk46XU_ghQo4diw@mail.gmail.com>
Li Wang <liwang@redhat.com> writes:
> Hi,
>
> ltp/mprotect04[1] crashed by SEGV_PKUERR on ppc64(LPAR on P730, Power 8
> 8247-22L) with kernel-v4.16.0-rc4.
>
> 10000000-10020000 r-xp 00000000 fd:00 167223 mprotect04
> 10020000-10030000 r--p 00010000 fd:00 167223 mprotect04
> 10030000-10040000 rw-p 00020000 fd:00 167223 mprotect04
> 1001a380000-1001a3b0000 rw-p 00000000 00:00 0 [heap]
> 7fffa6c60000-7fffa6c80000 --xp 00000000 00:00 0
>
> &exec_func = 0x10030170
>
> &func = 0x7fffa6c60170
>
> While perform
> "(*func)();" we get the
> segmentation fault.
>
>
> strace log:
>
> -------------------
> mprotect(0x7fffaed00000, 131072, PROT_EXEC) = 0
> rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_PKUERR, si_addr=0x7fffaed00170}
> ---
Looks like a bug to me.
Please Cc linuxppc-dev on powerpc bugs.
I also can't reproduce this failure on my machine.
Not sure what's going on?
cheers
next prev parent reply other threads:[~2018-03-08 12:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 8:09 Li Wang
2018-03-08 0:43 ` Ram Pai
2018-03-08 3:38 ` Li Wang
2018-03-08 12:19 ` Michael Ellerman [this message]
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
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=871sguep4v.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=jstancek@redhat.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.orglinuxppc-dev \
--cc=linuxram@us.ibm.com \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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