From: "H.J. Lu" <hjl.tools@gmail.com>
To: Siddhesh Poyarekar <siddhesh@sourceware.org>
Cc: 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: Wed, 15 Sep 2021 09:34:56 -0700 [thread overview]
Message-ID: <CAMe9rOpwR0dotYyEsvdbj3d56sTRj_fMFQu-QEUP4Pywr3o6Sg@mail.gmail.com> (raw)
In-Reply-To: <ea957fa1-9fc0-cd6a-75d2-ffb2625687e7@sourceware.org>
On Wed, Sep 15, 2021 at 9:24 AM Siddhesh Poyarekar
<siddhesh@sourceware.org> wrote:
>
> On 9/15/21 9:43 PM, H.J. Lu via Libc-alpha wrote:
> > Can you extract logic from setup_vdso to handle DSOs without
> > relocations?
>
> The logic is already in elf_get_dynamic_info; setup_vdso only supplies
> the static temp buffer to store the adjustments. We could dynamically
> allocate memory for every DSO that has a read-only dynamic segment and
> put the adjustments there, pointing l->l_info pointers to it, but is it
> really necessary? What's the use case for a DSO with a read-only
> dynamic segment?
>
> Siddhesh
I think there are 2 separate, but related cases: read-only dynamic
segment and DSOs without relocations.
--
H.J.
next prev parent reply other threads:[~2021-09-15 16:35 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 [this message]
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
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=CAMe9rOpwR0dotYyEsvdbj3d56sTRj_fMFQu-QEUP4Pywr3o6Sg@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@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).