This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Linux: Implement interfaces for memory protection keys

From: Florian Weimer <fweimer at redhat dot com>
To: libc-alpha at sourceware dot org
Date: Sun, 5 Nov 2017 08:33:15 +0100
Subject: Re: [PATCH] Linux: Implement interfaces for memory protection keys
Authentication-results: sourceware.org; auth=none
Authentication-results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=fweimer at redhat dot com
Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com B02CD356F0
References: <20171104174948.A79F6400EA2DF@oldenburg.str.redhat.com>

On 11/04/2017 06:49 PM, Florian Weimer wrote:

This adds system call wrappers for pkey_alloc, pkey_free, pkey_mprotect,
and x86-64 implementations of pkey_get and pkey_set, which abstract over
the PKRU CPU register and hide the actual number of memory protection
keys supported by the CPU.

The system call wrapers use unsigned int instead of unsigned long for
parameters, so that no special treatment for x32 is needed.  The flags
argument is currently unused, and the access rights bit mask is limited
to two bits by the current PKRU register layout anyway.


I again forgot to add a NEWS entry.

Note that the manual pages for pkey_alloc etc. are currently quiteconfusing (and we'd have to add one for pkey_set/pkey_get).


Thanks,
Florian

Follow-Ups:
- Re: [PATCH] Linux: Implement interfaces for memory protection keys
  - From: Joseph Myers

References:
- [PATCH] Linux: Implement interfaces for memory protection keys
  - From: Florian Weimer

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]