public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH 1/3] CET: Rename CET_MAX to CET_CONTROL_MASK [BZ #25887]
Date: Sat, 16 May 2020 19:27:18 +0200	[thread overview]
Message-ID: <871rnjoknd.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20200428215243.236312-2-hjl.tools@gmail.com> (H. J. Lu via Libc-alpha's message of "Tue, 28 Apr 2020 14:52:41 -0700")

* H. J. Lu via Libc-alpha:

> diff --git a/sysdeps/x86/cet-tunables.h b/sysdeps/x86/cet-tunables.h
> index 5e1e42df10..0088b89d3e 100644
> --- a/sysdeps/x86/cet-tunables.h
> +++ b/sysdeps/x86/cet-tunables.h
> @@ -16,14 +16,32 @@
>     License along with the GNU C Library; if not, see
>     <https://www.gnu.org/licenses/>.  */
>  
> -/* Valid control values:
> +#ifndef _CET_TUNABLES_H
> +#define _CET_TUNABLES_H
> +
> +/* For 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.
> +
> +   Bits 0-1: IBT
> +   Bits 2-3: SHSTK
>   */
>  #define CET_ELF_PROPERTY	0
>  #define CET_ALWAYS_OFF		1
>  #define CET_ALWAYS_ON		2
>  #define CET_PERMISSIVE		3
> -#define CET_MAX			CET_PERMISSIVE
> +#define CET_CONTROL_MASK	3
> +#define CET_IBT_SHIFT		0
> +#define CET_SHSTK_SHIFT		2
> +
> +/* Get CET control value.  */
> +
> +static inline unsigned int
> +get_cet_control_value (unsigned int shift)
> +{
> +  return (GL(dl_x86_feature_1)[1] >> shift) & CET_CONTROL_MASK;
> +}
> +
> +#endif /* cet-tunables.h */

Is there a reason why this has to be a single bitmask?  Maybe a
bitfield would better document the intent?

  parent reply	other threads:[~2020-05-16 17:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 21:52 [PATCH 0/3] x86: Add --enable-cet=permissive H.J. Lu
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 [this message]
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=871rnjoknd.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --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).