From: Florian Weimer <fweimer@redhat.com>
To: "Soni L." <fakedme+libc@gmail.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Libc-help <libc-help@sourceware.org>
Subject: Re: inode-based dlopen caching
Date: Tue, 08 Jun 2021 20:17:19 +0200 [thread overview]
Message-ID: <87czsw9q6o.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <f5916313-62bb-b22d-db60-8da7ca2c00a4@gmail.com> (Soni L.'s message of "Tue, 8 Jun 2021 15:10:02 -0300")
* Soni L.:
> The motivating use-case is hexchat plugins. Especially when they're
> written in Rust. Rust is supposed to provide memory safety but some
> edge-cases with dlopen break that, like truncating the shared library,
> or closing a shared library that has spawned threads.
Truncating the shared object will always cause problems until the kernel
implements MAP_COPY, or we stop mapping code in the dynamic loader.
Another option (implemented by GHC and others) is to have a customer
loader. Except for initial-exec memory and symbol interposition, there
is nothing magic at all about dlopen. Applications certainly can
implement their own object code loading mechanisms.
Thanks,
Florian
next prev parent reply other threads:[~2021-06-08 18:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 13:59 Soni L.
2021-06-07 21:53 ` Adhemerval Zanella
2021-06-07 22:50 ` Soni L.
2021-06-08 13:14 ` Adhemerval Zanella
2021-06-08 16:26 ` Soni L.
2021-06-08 16:51 ` Adhemerval Zanella
2021-06-08 16:56 ` Florian Weimer
2021-06-08 17:19 ` Adhemerval Zanella
2021-06-08 17:20 ` Florian Weimer
2021-06-08 18:10 ` Soni L.
2021-06-08 18:17 ` Florian Weimer [this message]
2021-06-08 19:25 ` Adhemerval Zanella
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=87czsw9q6o.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=fakedme+libc@gmail.com \
--cc=libc-help@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).