From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 31878@debbugs.gnu.org
Subject: bug#31878: Module autoloading is not thread safe
Date: Thu, 23 Aug 2018 15:54:00 +0200 [thread overview]
Message-ID: <87va81p4sn.fsf@gnu.org> (raw)
In-Reply-To: <87woshbzak.fsf@netris.org> (Mark H. Weaver's message of "Wed, 22 Aug 2018 22:18:59 -0400")
Mark H Weaver <mhw@netris.org> skribis:
> I forgot to mention an important aspect of the proposed auto-load
> locking here. It would not be a global lock, but rather a lock specific
> to the module being loaded. So, I guess we would need a global table of
> locks for modules-being-loaded.
Right (we can’t add a mutex to the module record without breaking the
ABI.)
> Since Guile (unfortunately) allows cyclic module dependencies, we would
> need a mechanism to avoid deadlocks in case modules A and B both import
> each other, and two threads concurrently attempt to load those modules.
>
> The first idea that comes to mind is to also have a global structure
> storing a partial order on the modules currently being loaded. If,
> while module A is being loaded, there's an attempt to auto-load module
> B, then an entry (A < B) would added to the partial order. The partial
> order would not allow cycles to be introduced, reporting an error in
> that case. In case a cycle would be introduced when adding (A < B),
> then the thread would simply be given access to the partially-loaded
> module B, by adding B to its local list of modules-being-loaded.
Would it enough to (1) use recursive mutexes, and (2) have
‘resolve-module’ lookup modules first in the global name space, and
second in the local list of modules being loaded?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-08-23 13:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 9:43 bug#31878: Module autoloading is not thread safe Ludovic Courtès
2018-06-18 11:11 ` Ludovic Courtès
2018-06-18 12:17 ` Ludovic Courtès
2018-08-22 23:22 ` Mark H Weaver
2018-08-23 2:18 ` Mark H Weaver
2018-08-23 13:54 ` Ludovic Courtès [this message]
2018-08-23 19:40 ` Mark H Weaver
2018-08-24 8:45 ` Ludovic Courtès
2018-10-21 18:16 ` Mark H Weaver
2018-10-22 10:10 ` Ludovic Courtès
[not found] ` <876002dm18.fsf@netris.org>
2018-08-23 13:51 ` Ludovic Courtès
2022-04-04 11:47 ` Calvin Heim
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87va81p4sn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31878@debbugs.gnu.org \
--cc=mhw@netris.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).