public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Subject: [PATCH 0/3] Checking HWCAP bits against compiler flags
Date: Thu, 06 May 2021 14:30:02 +0200	[thread overview]
Message-ID: <cover.1620304013.git.fweimer@redhat.com> (raw)

This series adds checks after HWCAP parsing that all bits required for
compiler flags are present.  It is brittle by design because invalid
instructions could already have been used by the dynamic loader at this
point, but for our downstream use case, it is an improvement over a
plain SIGILL.  (If this is deemed too hackish, I'll probably revert our
downstream changes.)

Tested on various variants on z13, z15, POWER8 and POWER9, and also
built with build-many-glibcs.py.

Thanks,
Florian

Florian Weimer (3):
  elf: Add hook for checking HWCAP bits after auxiliary vector parsing
  powerpc64le: Check HWCAP bits against compiler build flags
  s390x: Check HWCAP bits against compiler flags

 elf/dl-sysdep.c                               |  3 ++
 sysdeps/generic/dl-hwcap-check.h              | 28 +++++++++++
 sysdeps/powerpc/powerpc64/le/dl-hwcap-check.h | 49 +++++++++++++++++++
 sysdeps/s390/s390-64/dl-hwcap-check.h         | 40 +++++++++++++++
 4 files changed, 120 insertions(+)
 create mode 100644 sysdeps/generic/dl-hwcap-check.h
 create mode 100644 sysdeps/powerpc/powerpc64/le/dl-hwcap-check.h
 create mode 100644 sysdeps/s390/s390-64/dl-hwcap-check.h

-- 
2.30.2


             reply	other threads:[~2021-05-06 12:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 12:30 Florian Weimer [this message]
2021-05-06 12:30 ` [PATCH 1/3] elf: Add hook for checking HWCAP bits after auxiliary vector parsing Florian Weimer
2021-05-12  7:43   ` Stefan Liebler
2021-05-06 12:30 ` [PATCH 2/3] powerpc64le: Check HWCAP bits against compiler build flags Florian Weimer
2021-05-11 21:12   ` Lucas A. M. Magalhaes
2021-05-12  8:27     ` Florian Weimer
2021-05-12 14:50       ` Lucas A. M. Magalhaes
2021-05-12 14:52       ` Tulio Magno Quites Machado Filho
2021-05-12 17:27         ` Florian Weimer
2021-05-12 19:24           ` Tulio Magno Quites Machado Filho
2021-05-18 16:59         ` Florian Weimer
2021-05-18 17:26           ` Tulio Magno Quites Machado Filho
2021-05-18 17:41             ` Florian Weimer
2021-05-06 12:30 ` [PATCH 3/3] s390x: Check HWCAP bits against compiler flags Florian Weimer
2021-05-12  7:43   ` Stefan Liebler

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=cover.1620304013.git.fweimer@redhat.com \
    --to=fweimer@redhat.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).