public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: H.J. Lu <hjl@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Deleted branch hjl/cet/master
Date: Tue, 28 Apr 2020 17:59:45 +0000 (GMT)	[thread overview]
Message-ID: <20200428175945.0A2513851C11@sourceware.org> (raw)

The branch 'hjl/cet/master' was deleted.
It previously pointed to:

 e772a01f9c... Fix test

Diff:

!!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST):
-------------------------------------------------------------------

  e772a01... Fix test
  d0ce483... x86: Add --enable-cet=permissive
  f9a69d5... rtld: Get architecture specific initializer in rtld_global
  97547c7... CET: Rename CET_MAX to CET_CONTROL_MASK [BZ #25887]

commit e772a01f9cdbf8e9d824f793301437ff0bd725a6
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Tue Apr 28 10:57:24 2020 -0700

    Fix test

commit d0ce483f4c16edf07d6e2a3a028c7f15388f4735
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Mon Apr 27 15:44:07 2020 -0700

    x86: Add --enable-cet=permissive
    
    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.
    
    Add DEFAULT_DL_X86_FEATURE_1_1 to config.h.in:
    
     /* The default value of _dl_x86_feature_1[1].  */
     #define DEFAULT_DL_X86_FEATURE_1_1 0
    
    --enable-cet changes it to
    
     /* The default value of _dl_x86_feature_1[1].  */
     #define DEFAULT_DL_X86_FEATURE_1_1 ((CET_ELF_PROPERTY << CET_IBT_SHIFT) | (CET_ELF_PROPERTY << CET_SHSTK_SHIFT))
    
    enables CET features based on ELF property note.
    
    --enable-cet=permissive it to
    
     /* The default value of _dl_x86_feature_1[1].  */
     #define DEFAULT_DL_X86_FEATURE_1_1 ((CET_PERMISSIVE << CET_IBT_SHIFT) | (CET_PERMISSIVE << CET_SHSTK_SHIFT))
    
    which enable CET features permissively.

commit f9a69d5fd4c9a3fd4435b6e58a818e3ebe198b00
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Tue Apr 28 10:05:25 2020 -0700

    rtld: Get architecture specific initializer in rtld_global
    
    Include <dl-procruntime.c> to get architecture specific initializer in
    rtld_global.

commit 97547c772180b927531ce073dd55f2bf646a133d
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Tue Apr 28 07:46:17 2020 -0700

    CET: Rename CET_MAX to CET_CONTROL_MASK [BZ #25887]
    
    _dl_x86_feature_1[1] is used to control each CET feature, IBT and SHSTK:
    
     /* Valid control values:
        0: Enable CET features based on ELF property note.
        1: Always disable CET features.
        2: Always enable CET features.
        3: Enable CET features permissively.
      */
     #define CET_ELF_PROPERTY       0
     #define CET_ALWAYS_OFF         1
     #define CET_ALWAYS_ON          2
     #define CET_PERMISSIVE         3
     #define CET_MAX                CET_PERMISSIVE
    
    CET control value takes 2 bits.  Rename CET_MAX to CET_CONTROL_MASK.  Add
    CET_IBT_SHIFT and CET_SHSTK_SHIFT.


                 reply	other threads:[~2020-04-28 17:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200428175945.0A2513851C11@sourceware.org \
    --to=hjl@sourceware.org \
    --cc=glibc-cvs@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).