public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/26717] New: Detect incompatible shared libraries
Date: Thu, 08 Oct 2020 12:59:41 +0000	[thread overview]
Message-ID: <bug-26717-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26717
           Summary: Detect incompatible shared libraries
           Product: glibc
           Version: 2.33
            Status: NEW
          Severity: normal
          Priority: P2
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: hjl.tools at gmail dot com
                CC: fweimer at redhat dot com
  Target Milestone: 2.33
            Target: x86-64

When an x86-64-v4 shared library is placed in the x86-64-v2 directory by
mistake on a x86-64-v2 machine, the program may run for a while and then
crashes on x86-64-v4 instructions.  The linker with -z x86-64-v[234]

https://sourceware.org/pipermail/binutils/2020-October/113633.html

can add an x86-64-v[234] marker.  In addition to EM_X86_64, the
GNU_PROPERTY_X86_ISA_1_V[234] marker can be used by ld.so to detect
the x86-64-v4 shared library placed in an x86-64-v2 directory to
avoid crashes on x86-64-v4 instructions.

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

                 reply	other threads:[~2020-10-08 12: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=bug-26717-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).