From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] Linux: Implement interfaces for memory protection keys
Date: Sun, 05 Nov 2017 07:35:00 -0000 [thread overview]
Message-ID: <119f085e-b238-af55-e4fe-e2132a29fec6@redhat.com> (raw)
In-Reply-To: <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 quite
confusing (and we'd have to add one for pkey_set/pkey_get).
Thanks,
Florian
next prev parent reply other threads:[~2017-11-05 7:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 17:49 Florian Weimer
2017-11-05 7:35 ` Florian Weimer [this message]
2017-11-06 13:29 ` Joseph Myers
2017-11-06 13:40 ` Florian Weimer
2017-11-06 16:49 ` Adhemerval Zanella
2017-11-06 20:01 ` Florian Weimer
2017-11-06 21:46 ` Adhemerval Zanella
2017-11-06 22:03 ` Florian Weimer
2017-11-07 19:59 ` Adhemerval Zanella
2017-11-23 14:36 ` Florian Weimer
2017-11-28 19:02 ` Adhemerval Zanella
2017-12-01 16:30 ` Florian Weimer
2017-12-05 13:52 ` Florian Weimer
2017-12-05 14:06 ` Adhemerval Zanella
2017-12-05 14:18 ` Florian Weimer
2017-11-06 22:59 ` Joseph Myers
2017-11-07 2:16 ` Adhemerval Zanella
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=119f085e-b238-af55-e4fe-e2132a29fec6@redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).