From: Florian Weimer <fweimer@redhat.com>
To: Ram Pai <linuxram@us.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-mm <linux-mm@kvack.org>,
Dave Hansen <dave.hansen@intel.com>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: pkeys on POWER: Access rights not reset on execve
Date: Sat, 19 May 2018 07:12:19 +0200 [thread overview]
Message-ID: <d886e425-71fc-e203-e22d-7e07552c91c4@redhat.com> (raw)
In-Reply-To: <20180519011947.GJ5479@ram.oc3035372033.ibm.com>
On 05/19/2018 03:19 AM, Ram Pai wrote:
>> New AMR value (PID 112291, before execl): 0x0c00000000000000
>> AMR (PID 112291): 0x0c00000000000000
The issue is here. The second line is after the execl (printed from the
start of main), and the AMR value is not reset to zero.
>> Allocated key (PID 112291): 2
>>
>> I think this is a real bug and needs to be fixed even if the
>> defaults are kept as-is (see the other thread).
>
> The issue you may be talking about here is that --
>
> "when you set the AMR register to 0xffffffffffffffff, it
> just sets it to 0x0c00000000000000."
>
> To me it looks like, exec/fork are not related to the issue.
> Or are they also somehow connected to the issue?
Yes, this is the other issue. It is not really important here.
Thanks,
Florian
next prev parent reply other threads:[~2018-05-19 5:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 14:27 pkeys on POWER: Access rights not reset on execve Florian Weimer
2018-05-19 1:19 ` Ram Pai
2018-05-19 1:50 ` Andy Lutomirski
2018-05-19 5:26 ` Florian Weimer
2018-05-19 20:27 ` Ram Pai
2018-05-19 23:47 ` Andy Lutomirski
2018-05-20 6:04 ` Ram Pai
2018-05-20 6:06 ` Andy Lutomirski
2018-05-20 19:11 ` Ram Pai
2018-05-21 11:29 ` Florian Weimer
2018-06-03 20:18 ` Ram Pai
2018-06-04 10:12 ` Florian Weimer
2018-06-04 14:01 ` Ram Pai
2018-06-04 17:57 ` Florian Weimer
2018-06-04 19:02 ` Ram Pai
2018-06-04 21:00 ` Florian Weimer
2018-06-08 2:34 ` Ram Pai
2018-06-08 5:53 ` Florian Weimer
2018-06-08 10:15 ` Michal Suchánek
2018-06-08 10:44 ` Florian Weimer
2018-06-08 12:54 ` Michal Suchánek
2018-06-08 12:57 ` Florian Weimer
2018-06-08 13:49 ` Michal Suchánek
2018-06-08 13:51 ` Florian Weimer
2018-06-08 14:17 ` Michal Suchánek
2018-06-11 17:23 ` Ram Pai
2018-06-11 17:29 ` Florian Weimer
2018-06-11 20:08 ` Ram Pai
2018-06-12 12:17 ` Florian Weimer
2018-05-19 5:12 ` Florian Weimer [this message]
2018-05-19 11:11 ` Florian Weimer
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=d886e425-71fc-e203-e22d-7e07552c91c4@redhat.com \
--to=fweimer@redhat.com \
--cc=dave.hansen@intel.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=luto@amacapital.net \
/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).