From: Dave Hansen <dave.hansen@intel.com>
To: "Michal Suchánek" <msuchanek@suse.de>, "Ram Pai" <linuxram@us.ibm.com>
Cc: mpe@ellerman.id.au, Ulrich.Weigand@de.ibm.com,
bsingharora@gmail.com, benh@kernel.crashing.org,
mhocko@kernel.org, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
aneesh.kumar@linux.vnet.ibm.com, bauerman@linux.vnet.ibm.com,
linuxppc-dev@lists.ozlabs.org, fweimer@redhat.com,
paulus@samba.org, hbabu@us.ibm.com
Subject: Re: [PATCH v3] powerpc, pkey: make protection key 0 less special
Date: Fri, 4 May 2018 14:31:10 -0700 [thread overview]
Message-ID: <edd3d544-9fa8-5a79-4325-818ee5d7dfb0@intel.com> (raw)
In-Reply-To: <20180504232647.3412f563@naga.suse.cz>
On 05/04/2018 02:26 PM, Michal Suchánek wrote:
> If it is not ok to change permissions of pkey 0 is it ok to free it?
It's pretty much never OK to free it on x86 or ppc. But, we're not
going to put code in to keep userspace from shooting itself in the foot,
at least on x86.
next prev parent reply other threads:[~2018-05-04 21:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 19:22 [PATCH v3] powerpc, pkey: make protection key 0 less special Ram Pai
2018-05-04 19:59 ` Dave Hansen
2018-05-04 20:21 ` Ram Pai
2018-05-04 21:26 ` Michal Suchánek
2018-05-04 21:31 ` Dave Hansen [this message]
2018-05-04 21:45 ` Ram Pai
2018-05-05 12:39 ` Michal Suchánek
2018-05-06 20:10 ` Ram Pai
2018-05-07 11:21 ` Michal Suchánek
2018-05-08 16:38 ` Ram Pai
2018-05-08 17:03 ` Michal Suchánek
2018-05-08 18:38 ` Ram Pai
2018-05-09 15:43 ` Michal Suchánek
2018-05-09 15:46 ` Dave Hansen
2018-05-09 15:56 ` Michal Suchánek
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=edd3d544-9fa8-5a79-4325-818ee5d7dfb0@intel.com \
--to=dave.hansen@intel.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bauerman@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bsingharora@gmail.com \
--cc=fweimer@redhat.com \
--cc=hbabu@us.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=mhocko@kernel.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=msuchanek@suse.de \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.