From: Florian Weimer <fweimer@redhat.com>
To: "Soni L. via Libc-help" <libc-help@sourceware.org>
Subject: Re: inode-based dlopen caching
Date: Tue, 08 Jun 2021 18:56:47 +0200 [thread overview]
Message-ID: <87zgw09tww.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <d3044961-ff2e-ef1c-4ba1-b14ab73d2012@gmail.com> (Soni L. via Libc-help's message of "Sat, 5 Jun 2021 10:59:40 -0300")
* Soni L. via Libc-help:
> Currently dlopen caching is based on filenames, it'd be nice if it was
> based on inodes to support better "re"loading (aka loading a new module
> with the same name because unloading modules with threads is never a
> good idea). This is good for stuff that deals with plugins.
It's an interesting idea. We'd probably also want a flag that hides the
symbols from general binding and makes them available for direct dlsym
lookups using the handle returned by dlopen (otherwise the old
definitions stick around).
The tricky question is what to do about dependencies. A behavioral
change for just one level is not too hard, but everything goes further
is difficult.
Vivek Das Mohapatra's RTLD_SHARED patches may help with isolating
dependencies.
Thanks,
Florian
next prev parent reply other threads:[~2021-06-08 16:56 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 [this message]
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
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=87zgw09tww.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.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).