From: Yu-cheng Yu <yu-cheng.yu@intel.com>
To: linux-man@vger.kernel.org
Cc: Yu-cheng Yu <yu-cheng.yu@intel.com>
Subject: [PATCH 0/2] sigaction.2: Updates for SEGV_CPERR
Date: Fri, 26 Feb 2021 09:26:32 -0800 [thread overview]
Message-ID: <20210226172634.26905-1-yu-cheng.yu@intel.com> (raw)
Control-flow Enforcement [1] [2] introduces a new control-protection fault,
which is triggered by a branch instruction (call, ret, or jmp) violating
branch-enforcement rules. When the signal is delivered, si_code is set to
SEGV_CPERR. Add the code to sigaction.2, and while at it, clarify when
si_addr is set.
[1] Intel 64 and IA-32 Architectures Software Developer's Manual:
https://software.intel.com/en-us/download/intel-64-and-ia-32-
architectures-sdm-combined-volumes-1-2a-2b-2c-2d-3a-3b-3c-3d-and-4
[2] CET Shadow Stack patches v21:
https://lkml.kernel.org/r/20210217222730.15819-1-yu-cheng.yu@intel.com/
https://lkml.kernel.org/r/20210217223135.16790-1-yu-cheng.yu@intel.com/
Yu-cheng Yu (2):
sigaction.2: Add SEGV_CPERR
sigaction.2: wfix - Clarify si_addr description.
man2/sigaction.2 | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
--
2.21.0
next reply other threads:[~2021-02-26 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 17:26 Yu-cheng Yu [this message]
2021-02-26 17:26 ` [PATCH 1/2] sigaction.2: Add SEGV_CPERR Yu-cheng Yu
2021-02-26 17:26 ` [PATCH 2/2] sigaction.2: wfix - Clarify si_addr description Yu-cheng Yu
2021-03-08 21:30 ` Borislav Petkov
2021-03-08 21:46 ` Yu, Yu-cheng
2021-03-09 14:31 ` Borislav Petkov
[not found] ` <CACKs7VBLnQTc_RgnXk8X-XgVRvR5_uXY0wL0snW7P5iDjpb8fA@mail.gmail.com>
2021-03-11 17:33 ` Yu, Yu-cheng
2021-03-12 12:55 ` Stefan Puiu
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=20210226172634.26905-1-yu-cheng.yu@intel.com \
--to=yu-cheng.yu@intel.com \
--cc=linux-man@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).