public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/28340] ld.so crashes while loading a DSO with a read-only dynamic section
Date: Wed, 03 Nov 2021 09:59:10 +0000	[thread overview]
Message-ID: <bug-28340-131-COdP1f9Lcf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28340-131@http.sourceware.org/bugzilla/>

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

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.34/master branch has been updated by Florian Weimer
<fw@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=f42373f911a28d34325a5bfc1ed5a962c89da7eb

commit f42373f911a28d34325a5bfc1ed5a962c89da7eb
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Thu Sep 16 08:15:29 2021 -0700

    ld.so: Replace DL_RO_DYN_SECTION with dl_relocate_ld [BZ #28340]

    We can't relocate entries in dynamic section if it is readonly:

    1. Add a l_ld_readonly field to struct link_map to indicate if dynamic
    section is readonly and set it based on p_flags of PT_DYNAMIC segment.
    2. Replace DL_RO_DYN_SECTION with dl_relocate_ld to decide if dynamic
    section should be relocated.
    3. Remove DL_RO_DYN_TEMP_CNT.
    4. Don't use a static dynamic section to make readonly dynamic section
    in vDSO writable.
    5. Remove the temp argument from elf_get_dynamic_info.

    This fixes BZ #28340.

    Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
    (cherry picked from commit b413280cfb16834450f66f554bc0d618bb513851)

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

  parent reply	other threads:[~2021-11-03  9:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 17:46 [Bug dynamic-link/28340] New: " siddhesh at sourceware dot org
2021-09-14 17:46 ` [Bug dynamic-link/28340] " siddhesh at sourceware dot org
2021-09-22 18:14 ` cvs-commit at gcc dot gnu.org
2021-09-22 18:27 ` hjl.tools at gmail dot com
2021-09-24 16:27 ` fweimer at redhat dot com
2021-09-25 16:29 ` cvs-commit at gcc dot gnu.org
2021-10-19 13:41 ` cvs-commit at gcc dot gnu.org
2021-11-03  9:59 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-03  9:59 ` cvs-commit at gcc dot gnu.org
2021-11-03  9:59 ` cvs-commit at gcc dot gnu.org
2021-11-05  0:39 ` sam at gentoo dot org

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-28340-131-COdP1f9Lcf@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).