From: Florian Weimer <fweimer@redhat.com>
To: Dave Hansen <dave.hansen@linux.intel.com>,
linux-x86_64@vger.kernel.org, linux-arch@vger.kernel.org
Cc: linux-mm <linux-mm@kvack.org>, Linux API <linux-api@vger.kernel.org>
Subject: Re: MPK: pkey_free and key reuse
Date: Fri, 24 Nov 2017 15:55:28 +0100 [thread overview]
Message-ID: <2e3bfec2-303b-2221-0154-1145af3fffe8@redhat.com> (raw)
In-Reply-To: <04ef6b4a-6d20-d025-0b56-741fd467d445@linux.intel.com>
On 11/23/2017 04:25 PM, Dave Hansen wrote:
> I don't see a way to do a broadcast PKRU update. But, I'd love to be
> proven wrong, with code.
I could use the existing setxid broadcast code in glibc to update PKRU
on all running threads upon a key allocation (before pkey_alloc returns
to the application), but this won't work for the implicit protection key
used for PROT_EXEC. I don't see a good way to get its number, and to
determine whether a particular mprotect call allocated it. (We
obviously don't want to do the broadcast on every mprotect call with
PROT_EXEC, just in case.)
What's worse, the setxid broadcast is not async-signal-safe, so we can't
use it from mprotect, which should better be async-signal-safe (I know
that official, it's not, but it would still be problematic to change
that IMHO).
(The setxid broadcast mechanism allows us to run a piece of code on all
threads of the process. We could look at %rip and see if the signal
arrived during a pkey_set function call, and make sure that this call
delivers the right result, by altering the task state before returning.)
Thanks,
Florian
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Florian Weimer <fweimer@redhat.com>
To: Dave Hansen <dave.hansen@linux.intel.com>,
linux-x86_64@vger.kernel.org, linux-arch@vger.kernel.org
Cc: linux-mm <linux-mm@kvack.org>, Linux API <linux-api@vger.kernel.org>
Subject: Re: MPK: pkey_free and key reuse
Date: Fri, 24 Nov 2017 15:55:28 +0100 [thread overview]
Message-ID: <2e3bfec2-303b-2221-0154-1145af3fffe8@redhat.com> (raw)
Message-ID: <20171124145528.rK94aSktiL_UvpK35TUh_A8xpobwE57qz2VNPqPPqdM@z> (raw)
In-Reply-To: <04ef6b4a-6d20-d025-0b56-741fd467d445@linux.intel.com>
On 11/23/2017 04:25 PM, Dave Hansen wrote:
> I don't see a way to do a broadcast PKRU update. But, I'd love to be
> proven wrong, with code.
I could use the existing setxid broadcast code in glibc to update PKRU
on all running threads upon a key allocation (before pkey_alloc returns
to the application), but this won't work for the implicit protection key
used for PROT_EXEC. I don't see a good way to get its number, and to
determine whether a particular mprotect call allocated it. (We
obviously don't want to do the broadcast on every mprotect call with
PROT_EXEC, just in case.)
What's worse, the setxid broadcast is not async-signal-safe, so we can't
use it from mprotect, which should better be async-signal-safe (I know
that official, it's not, but it would still be problematic to change
that IMHO).
(The setxid broadcast mechanism allows us to run a piece of code on all
threads of the process. We could look at %rip and see if the signal
arrived during a pkey_set function call, and make sure that this call
delivers the right result, by altering the task state before returning.)
Thanks,
Florian
next prev parent reply other threads:[~2017-11-24 14:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 10:35 MPK: pkey_free and key reuse Florian Weimer
2017-11-05 10:35 ` Florian Weimer
2017-11-08 20:41 ` Dave Hansen
2017-11-09 14:48 ` Florian Weimer
2017-11-09 14:48 ` Florian Weimer
2017-11-09 16:59 ` Dave Hansen
2017-11-09 16:59 ` Dave Hansen
2017-11-23 12:48 ` Florian Weimer
2017-11-23 13:07 ` Vlastimil Babka
2017-11-23 13:07 ` Vlastimil Babka
2017-11-23 15:25 ` Dave Hansen
2017-11-24 14:55 ` Florian Weimer [this message]
2017-11-24 14:55 ` Florian Weimer
[not found] ` <0f006ef4-a7b5-c0cf-5f58-d0fd1f911a54-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-22 8:18 ` MPK: removing a pkey (was: pkey_free and key reuse) Vlastimil Babka
2017-11-22 8:18 ` Vlastimil Babka
2017-11-22 12:15 ` MPK: removing a pkey Florian Weimer
2017-11-22 12:15 ` Florian Weimer
2017-11-22 12:46 ` Vlastimil Babka
2017-11-22 12:46 ` Vlastimil Babka
[not found] ` <f0495f01-9821-ec36-56b4-333f109eb761-AlSwsSmVLrQ@public.gmane.org>
2017-11-22 12:49 ` Florian Weimer
2017-11-22 12:49 ` Florian Weimer
2017-11-22 16:10 ` Dave Hansen
2017-11-22 16:21 ` Florian Weimer
2017-11-22 16:21 ` Florian Weimer
[not found] ` <9ec19ff3-86f6-7cfe-1a07-1ab1c5d9882c-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-22 16:32 ` Dave Hansen
2017-11-22 16:32 ` Dave Hansen
2017-11-23 8:11 ` Vlastimil Babka
[not found] ` <de93997a-7802-96cf-62e2-e59416e745ca-AlSwsSmVLrQ@public.gmane.org>
2017-11-23 15:00 ` Dave Hansen
2017-11-23 15:00 ` Dave Hansen
2017-11-23 21:42 ` Vlastimil Babka
[not found] ` <2d12777f-615a-8101-2156-cf861ec13aa7-AlSwsSmVLrQ@public.gmane.org>
2017-11-23 23:29 ` Dave Hansen
2017-11-23 23:29 ` Dave Hansen
2017-11-24 8:35 ` Florian Weimer
2017-11-24 8:35 ` Florian Weimer
2017-11-24 8:38 ` Vlastimil Babka
2017-11-23 12:38 ` Florian Weimer
2017-11-23 15:09 ` 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=2e3bfec2-303b-2221-0154-1145af3fffe8@redhat.com \
--to=fweimer@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-x86_64@vger.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).