public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: libc-alpha@sourceware.org
Subject: [PATCH 0/3] x86: Add --enable-cet=permissive
Date: Tue, 28 Apr 2020 14:52:40 -0700	[thread overview]
Message-ID: <20200428215243.236312-1-hjl.tools@gmail.com> (raw)

When CET is enabled, it is an error to dlopen a non CET enabled shared
library in CET enabled application.  It may be desirable to make CET
permissive, that is disable CET when dlopening a non CET enabled shared
library.  With the new --enable-cet=permissive configure option, CET is
disabled when dlopening a non CET enabled shared library.

To support --enable-cet=permissive, CET_MAX is renamed to
CET_CONTROL_MASK and <dl-procruntime.c> is included in rtld.c to get
architecture specific initializer in rtld_global.

H.J. Lu (3):
  CET: Rename CET_MAX to CET_CONTROL_MASK [BZ #25887]
  rtld: Get architecture specific initializer in rtld_global
  x86: Add --enable-cet=permissive

 INSTALL                              | 26 +++++++++++--------
 config.h.in                          |  3 +++
 elf/rtld.c                           |  2 ++
 manual/install.texi                  | 12 ++++++---
 sysdeps/unix/sysv/linux/x86/Makefile |  2 +-
 sysdeps/x86/Makefile                 | 18 +++++++++----
 sysdeps/x86/cet-tunables.h           | 22 ++++++++++++++--
 sysdeps/x86/configure                | 21 ++++++++-------
 sysdeps/x86/configure.ac             | 19 +++++++-------
 sysdeps/x86/cpu-features.c           |  7 +++--
 sysdeps/x86/cpu-tunables.c           | 39 +++++++++++-----------------
 sysdeps/x86/dl-cet.c                 |  6 ++---
 sysdeps/x86/dl-procruntime.c         |  5 ++++
 sysdeps/x86/tst-cet-legacy-5.c       | 25 ++++++++++++------
 sysdeps/x86/tst-cet-legacy-6.c       | 25 ++++++++++++------
 15 files changed, 141 insertions(+), 91 deletions(-)

-- 
2.25.4


             reply	other threads:[~2020-04-28 21:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 21:52 H.J. Lu [this message]
2020-04-28 21:52 ` [PATCH 1/3] CET: Rename CET_MAX to CET_CONTROL_MASK [BZ #25887] H.J. Lu
2020-05-16 16:37   ` PING: " H.J. Lu
2020-05-16 17:27   ` Florian Weimer
2020-05-16 23:44     ` [PATCH] x86: Move CET control to _dl_x86_feature_control " H.J. Lu
2020-05-18  7:19       ` Florian Weimer
2020-05-18 12:26         ` V2 " H.J. Lu
2020-05-18 12:36           ` Florian Weimer
2020-04-28 21:52 ` [PATCH 2/3] rtld: Get architecture specific initializer in rtld_global H.J. Lu
2020-05-16 16:38   ` PING: " H.J. Lu
2020-05-16 17:51   ` Florian Weimer
2020-05-16 18:01     ` H.J. Lu
2020-05-16 18:07       ` Florian Weimer
2020-05-16 18:24         ` V2 [PATCH] " H.J. Lu
2020-04-28 21:52 ` [PATCH 3/3] x86: Add --enable-cet=permissive H.J. Lu
2020-04-29 17:19 ` [PATCH 0/3] " Adhemerval Zanella
2020-04-29 20:29   ` H.J. Lu
2020-04-29 20:46   ` Florian Weimer
2020-04-29 21:14     ` Adhemerval Zanella
2020-05-18 13:50       ` V2 [PATCH] " H.J. Lu
2020-05-18 14:43         ` Florian Weimer

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=20200428215243.236312-1-hjl.tools@gmail.com \
    --to=hjl.tools@gmail.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).