From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH v3 0/3] elf: Allow dlopen of filter object to work [BZ #16272]
Date: Wed, 18 Dec 2019 16:33:32 -0300 [thread overview]
Message-ID: <7905f81b-ac11-f097-11f8-3166340d932b@linaro.org> (raw)
In-Reply-To: <DB6PR0801MB17510453724EEABD8742854691530@DB6PR0801MB1751.eurprd08.prod.outlook.com>
On 18/12/2019 13:32, David Kilroy wrote:
>> Repost of v2 with updated commit message resulting from follow-up
>> tests with a different implementation.
>>
>> I'd still like to see this fixed, but the last patchset didn't get any
>> responses.
>>
>> v3:
>> - rebased for changes in elf/Makefile
>> - updates to commit messages
>>
>> v2:
>> https://sourceware.org/ml/libc-alpha/2019-10/msg00701.html
>> - code formatting fixups
>> - add dependency of test output on filtee library
>> - tests changed to use the test framework
>>
>> v1:
>> https://sourceware.org/ml/libc-alpha/2019-10/msg00519.html
>
> Ping. Is there any interest in taking this series, or something like it?
> I've seen that it needs another (almost trivial) rebase for changes in
> elf/Makefile, but don't want do that unnecessarily.
I think there is interest, the main problem is always lack of manpower
and time from reviewers to move this forward. I will try to spend some
time to review it.
>
> It seems wrong that the toolchain can build a library as a forwarding library,
> but it only works if you link against it normally (and not via dlopen).
>
> This BZ is also referenced from https://gitlab.freedesktop.org/glvnd/libglvnd#issues
>
> We came across this as we were exploring different ways to support multiple
> stub libraries that at runtime forward to a single implementation library.
> The Solaris-like forwarding libraries are nice for this, as the forwarding is
> encapsulated in the compiled library. What we end up doing is still under
> consideration - we have a few options including link scripts+symlinks as
> proposed by Florian in [1]. The different solutions have drawbacks for us,
> so having dlopen'able forwarding libraries would help by giving us another
> option.
>
Thanks for the links, I see that this issue comes and go with different
solutions that hack into the loader (like that dlmopen namespace proposal
sometime ago). At least this seems to fix an already available solution
and also adds some code refactor and cleanup.
>
> Thanks,
>
> Dave Kilroy.
>
> [1] - https://sourceware.org/ml/libc-alpha/2019-10/msg00619.html
>
next prev parent reply other threads:[~2019-12-18 19:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 17:30 [PATCH v3 0/3] elf: Allow dlopen of filter object to work [BZ #16272] David Kilroy
2019-12-03 17:30 ` [PATCH v3 1/3] " David Kilroy
2020-01-14 18:30 ` Adhemerval Zanella
2020-01-15 12:03 ` David Kilroy
2020-01-17 13:35 ` Adhemerval Zanella
2020-01-17 16:38 ` David Kilroy
2020-01-21 15:59 ` David Kilroy
2020-01-22 20:27 ` Adhemerval Zanella
2019-12-03 17:30 ` [PATCH v3 3/3] elf: avoid stack allocation in dl_open_worker David Kilroy
2020-01-14 20:04 ` Adhemerval Zanella
2019-12-03 17:30 ` [PATCH v3 2/3] elf: avoid redundant sort in dlopen David Kilroy
2020-01-14 19:41 ` Adhemerval Zanella
2019-12-18 16:32 ` [PATCH v3 0/3] elf: Allow dlopen of filter object to work [BZ #16272] David Kilroy
2019-12-18 19:33 ` Adhemerval Zanella [this message]
2019-12-19 11:42 ` David Kilroy
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7905f81b-ac11-f097-11f8-3166340d932b@linaro.org \
--to=adhemerval.zanella@linaro.org \
--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).