linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linuxram@us.ibm.com, mpe@ellerman.id.au, mingo@kernel.org,
	akpm@linux-foundation.org, shuah@kernel.org
Subject: Re: [PATCH 1/3] x86, pkeys: do not special case protection key 0
Date: Sat, 17 Mar 2018 20:05:12 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.1803172004130.1509@nanos.tec.linutronix.de> (raw)
In-Reply-To: <6e0c687d-f465-5433-10be-db04489278a9@intel.com>

On Sat, 17 Mar 2018, Dave Hansen wrote:
> On 03/17/2018 02:12 AM, Thomas Gleixner wrote:
> >> This is a bit nicer than what Ram proposed because it is simpler
> >> and removes special-casing for pkey 0.  On the other hand, it does
> >> allow applciations to pkey_free() pkey-0, but that's just a silly
> >> thing to do, so we are not going to protect against it.
> > What's the consequence of that? Application crashing and burning itself or
> > something more subtle?
> 
> You would have to:
> 
> 	pkey_free(0)
> 	... later
> 	new_key = pkey_alloc();
> 	// now new_key=0
> 	pkey_deny_access(new_key); // or whatever
> 
> At which point most apps would probably croak because its stack is
> inaccessible.  The free itself does not make the key inaccessible, *but*
> we could also do that within the existing ABI if we want.  I think I
> called out that behavior as undefined in the manpage.

As long as its documented and the change only allows people to shoot them
more in the foot, we're all good.

Thanks,

	tglx

  reply	other threads:[~2018-03-17 19:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 21:46 [PATCH 0/3] x86, pkeys: make pkey 0 more normal Dave Hansen
2018-03-16 21:46 ` [PATCH 1/3] x86, pkeys: do not special case protection key 0 Dave Hansen
2018-03-17  9:12   ` Thomas Gleixner
2018-03-17 16:01     ` Dave Hansen
2018-03-17 19:05       ` Thomas Gleixner [this message]
2018-03-19  5:50       ` Michael Ellerman
2018-03-17 23:24   ` Ram Pai
2018-03-18  0:49     ` Dave Hansen
2018-03-18  9:30     ` Thomas Gleixner
2018-03-18 23:46       ` Ram Pai
2018-03-16 21:46 ` [PATCH 2/3] x86, pkeys, selftests: save off 'prot' for allocations Dave Hansen
2018-03-16 21:46 ` [PATCH 3/3] x86, pkeys, selftests: add a test for pkey 0 Dave Hansen

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=alpine.DEB.2.21.1803172004130.1509@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxram@us.ibm.com \
    --cc=mingo@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=shuah@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