public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
	Florian Weimer <fweimer@redhat.com>,
	 GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] ld.so: Handle read-only dynamic section gracefully [BZ #28340]
Date: Fri, 17 Sep 2021 08:17:16 +0530	[thread overview]
Message-ID: <abe4e783-73e0-465a-403f-b240bb206129@sourceware.org> (raw)
In-Reply-To: <CAMe9rOqJXj07UT4LMaL9oxS_RBGJd92wFThxtbQR6OdGRQaqTw@mail.gmail.com>

On 9/17/21 3:41 AM, H.J. Lu wrote:
>> 2. Do we want to leave .dynamic unrelocated for read-only DYNAMIC or
>> should we instead allocate an array to write relocated addresses in
>> there, like we did for vdso?
> 
> My patch removed the hack for vDSO to leave the read-only
> PT_DYNAMIC segment unrelocated.

Presuming that your rationale for this is your response from your other 
email:

> Non-glibc consumers of
> PT_DYNAMIC segment need to handle it differently for these non-ABI
> conforming binaries.

could you qualify this a bit more?  My reading of the spec[1] suggests 
that the spec is silent on whether the .dynamic entries should be 
writable, it merely says that the dynamic linker reads d_un.d_ptr and 
adds the memory base address to it when referring to those addresses. 
So calling them non-conforming seems wrong.

And if they're conforming, there seems to be little reason to make them 
different from DSOs with writable DYNAMIC segment as far as l_info data 
returned from dl_iterate_phdr is concerned.

Siddhesh

[1] https://refspecs.linuxbase.org/elf/gabi4+/ch5.dynamic.html

  reply	other threads:[~2021-09-17  2:47 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 19:09 Siddhesh Poyarekar
2021-09-14 19:15 ` Florian Weimer
2021-09-15  1:14   ` Siddhesh Poyarekar
2021-09-15 14:35 ` H.J. Lu
2021-09-15 15:42   ` Siddhesh Poyarekar
2021-09-15 16:13     ` H.J. Lu
2021-09-15 16:24       ` Siddhesh Poyarekar
2021-09-15 16:34         ` H.J. Lu
2021-09-16  1:43           ` Siddhesh Poyarekar
2021-09-16  2:23             ` H.J. Lu
2021-09-16  3:46               ` Siddhesh Poyarekar
2021-09-16  4:26                 ` H.J. Lu
2021-09-16  4:28                   ` Siddhesh Poyarekar
2021-09-16  4:30                     ` H.J. Lu
2021-09-16  4:48               ` Florian Weimer
2021-09-16  5:36                 ` Siddhesh Poyarekar
2021-09-16  5:46                   ` Florian Weimer
2021-09-16  6:04                     ` Siddhesh Poyarekar
2021-09-16 14:11                 ` Carlos O'Donell
2021-09-16 15:18                   ` H.J. Lu
2021-09-16 16:45                     ` Siddhesh Poyarekar
2021-09-16 17:38                       ` H.J. Lu
2021-09-16 17:58                         ` Siddhesh Poyarekar
2021-09-16 22:11                           ` H.J. Lu
2021-09-17  2:47                             ` Siddhesh Poyarekar [this message]
2021-09-17  2:59                               ` H.J. Lu
2021-09-17  3:36                                 ` Siddhesh Poyarekar
2021-09-17  3:42                                   ` H.J. Lu
2021-09-17  3:44                                     ` Siddhesh Poyarekar
2021-09-17  3:44                                   ` Florian Weimer
2021-09-17  3:51                                     ` Siddhesh Poyarekar
2021-09-16 18:03                         ` Florian Weimer
2021-09-16 22:14                           ` H.J. Lu
2021-09-17  2:58                           ` Siddhesh Poyarekar
2021-09-17  3:46                             ` Florian Weimer
2021-09-17  4:00                               ` Florian Weimer
2021-09-17  4:12                                 ` [PATCH] ld.so: Remove DL_RO_DYN_SECTION H.J. Lu
2021-09-17  6:54                                   ` David Abdurachmanov
2021-09-17  9:01                                   ` Siddhesh Poyarekar
2021-09-17 15:40                                     ` H.J. Lu
2021-10-14 12:36                               ` [PATCH] ld.so: Handle read-only dynamic section gracefully [BZ #28340] Maciej W. Rozycki

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=abe4e783-73e0-465a-403f-b240bb206129@sourceware.org \
    --to=siddhesh@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.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).