Issue #17420 has been updated by duerst (Martin D=FCrst).


I agree that it would be best to make require work everywhere, but always b=
e executed in the main Reactor. That would just be part of the semantics of=
 require (comment moved from #17477).

----------------------------------------
Bug #17420: Unsafe mutation of $" when doing non-RubyGems require in Ractor
https://bugs.ruby-lang.org/issues/17420#change-89598

* Author: Eregon (Benoit Daloze)
* Status: Open
* Priority: Normal
* Assignee: ko1 (Koichi Sasada)
* ruby -v: ruby 3.0.0dev (2020-12-16T10:12:48Z master a9a7f4d8b8) [x86_64-l=
inux]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
With an empty file `a.rb`:
```
$ ruby --disable-gems -e 'Ractor.new { puts $" }.take'
-e:1:in `block in <main>': can not access global variables $" from non-main=
 Ractors (RuntimeError)
```
That is expected, given the rules for global variables.

```
ruby --disable-gems -e 'Ractor.new { require "./a.rb"; }.take; p $"'
[... , "/home/eregon/a.rb"]
```
Is it OK that the Ractor can do `require`, which does modify `$"`?

I think it's not, and it might lead to segfaults if e.g. the main Ractor mu=
tates `$"` in parallel to some other Ractor doing `require`.

Probably `require` needs to be forbidden in non-main Ractors (it does mutat=
e `$"`, so it's logical), or there needs to be always VM-global synchroniza=
tion on any access to `$"` (otherwise, segfaults are possible).
The latter doesn't seem reasonable, especially when considering the user mi=
ght do `$".each { ... }`.

---

Note that RubyGems' `require` does not work on non-main Ractors (pretty muc=
h expected given it depends on a lot of global state):
```
$ ruby -e 'Ractor.new { require "./a.rb"; }.take'
<internal:/home/eregon/prefix/ruby-master/lib/ruby/3.0.0/rubygems/core_ext/=
kernel_require.rb>:37:in `require': can not access non-shareable objects in=
 constant Kernel::RUBYGEMS_ACTIVATION_MONITOR by non-main ractor. (NameErro=
r)
```

This probably also has consequences for `autoload`.
Maybe the `zeitwerk` gem can help with the mode to resolve all autoload at =
once.



-- =

https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=3Dunsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>