From: Florian Weimer <fweimer@redhat.com>
To: linux-mm <linux-mm@kvack.org>,
linux-arch <linux-arch@vger.kernel.org>,
linux-x86_64@vger.kernel.org,
Linux API <linux-api@vger.kernel.org>,
x86@kernel.org, Dave Hansen <dave.hansen@intel.com>,
Ram Pai <linuxram@us.ibm.com>
Subject: [PATCH] mm, x86: pkeys: Introduce PKEY_ALLOC_SIGNALINHERIT and change signal semantics
Date: Wed, 3 Jan 2018 13:31:25 +0100 [thread overview]
Message-ID: <360ef254-48bc-aee6-70f9-858f773b8693@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
This patch is based on the previous discussion (pkeys: Support setting
access rights for signal handlers):
https://marc.info/?t=151285426000001
It aligns the signal semantics of the x86 implementation with the
upcoming POWER implementation, and defines a new flag, so that
applications can detect which semantics the kernel uses.
A change in this area is needed to make memory protection keys usable
for protecting the GOT in the dynamic linker.
(Feel free to replace the trigraphs in the commit message before
committing, or to remove the program altogether.)
Thanks,
Florian
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: pkeys-signalinherit.patch --]
[-- Type: text/x-patch; name="pkeys-signalinherit.patch", Size: 0 bytes --]
next reply other threads:[~2018-01-03 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 12:31 Florian Weimer [this message]
2018-01-12 12:55 ` [REGRESSION] testing/selftests/x86/ pkeys build failures (was: Re: [PATCH] mm, x86: pkeys: Introduce PKEY_ALLOC_SIGNALINHERIT and change signal semantics) Ingo Molnar
2018-01-12 13:15 ` [REGRESSION] testing/selftests/x86/ pkeys build failures Florian Weimer
2018-01-16 2:37 ` Ingo Molnar
2018-01-12 14:14 ` [REGRESSION] testing/selftests/x86/ pkeys build failures (was: Re: [PATCH] mm, x86: pkeys: Introduce PKEY_ALLOC_SIGNALINHERIT and change signal semantics) Ingo Molnar
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=360ef254-48bc-aee6-70f9-858f773b8693@redhat.com \
--to=fweimer@redhat.com \
--cc=dave.hansen@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 \
--cc=linuxram@us.ibm.com \
--cc=x86@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