From: Florian Weimer <fweimer@redhat.com>
To: Ram Pai <linuxram@us.ibm.com>
Cc: Linux-MM <linux-mm@kvack.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@intel.com>
Subject: Re: pkeys on POWER: Access rights not reset on execve
Date: Tue, 12 Jun 2018 14:17:21 +0200 [thread overview]
Message-ID: <c2931344-d2e8-46c0-b70c-97567ae7f7a0@redhat.com> (raw)
In-Reply-To: <20180611200807.GA5773@ram.oc3035372033.ibm.com>
On 06/11/2018 10:08 PM, Ram Pai wrote:
> Ok. try this patch. This patch is on top of the 5 patches that I had
> sent last week i.e "[PATCH 0/5] powerpc/pkeys: fixes to pkeys"
>
> The following is a draft patch though to check if it meets your
> expectations.
>
> commit fe53b5fe2dcb3139ea27ade3ae7cbbe43c4af3be
> Author: Ram Pai<linuxram@us.ibm.com>
> Date: Mon Jun 11 14:57:34 2018 -0500
>
> powerpc/pkeys: Deny read/write/execute by default
With this patch, my existing misc/tst-pkey test in glibc passes. The
in-tree version still has some incorrect assumptions on implementation
behavior, but those are test bugs. The kernel behavior with your patch
look good to me. Thanks.
Florian
next prev parent reply other threads:[~2018-06-12 12:17 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 [this message]
2018-05-19 5:12 ` Florian Weimer
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=c2931344-d2e8-46c0-b70c-97567ae7f7a0@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@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 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).