public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fw at deneb dot enyo.de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/25938] New: ld.so.cache should store meaning of hwcap mask bits
Date: Thu, 07 May 2020 10:24:11 +0000	[thread overview]
Message-ID: <bug-25938-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=25938

            Bug ID: 25938
           Summary: ld.so.cache should store meaning of hwcap mask bits
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: minor
          Priority: P3
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: fw at deneb dot enyo.de
  Target Milestone: ---
             Flags: security-

The meaning of the bits depends on the glibc version: _DL_FIRST_EXTRA depends
on _DL_FIRST_PLATFORM and _DL_PLATFORMS_COUNT, and the latter increases if more
platform subdirectories are added (e.g., "power9").

This does not appear to be a significant issue today because the
_DL_FIRST_EXTRA mechanism was only ever used for the i686 nosegneg bit, and on
i686, _DL_FIRST_EXTRA has been unchanged for a long time.

The always-set bit for  the "tls" subdirectory is put by ldconfig at the MSB of
the 64-bit hwcap word, so its position is already constant.

However, if we ever want to reuse hwcap bits for different CPU features, the
cache needs to contain additional information about the meaning of the bits.
One way to express this mean is to list the subdirectory names the bits
correspond to.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-05-07 10:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 10:24 fw at deneb dot enyo.de [this message]
2020-12-04  8:52 ` [Bug dynamic-link/25938] " fweimer at redhat dot com

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=bug-25938-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).