From: Eric Wong <normalperson@...>
Date: 2018-11-18T08:19:41+00:00
Subject: [ruby-core:89853] Re: [Ruby trunk Bug#15316] rb_postponed_job_register not thread-safe

takashikkbn@gmail.com wrote:
> Oh by the way, I have a patch which was created yesterday but
> I was too busy to commit that yet. (I'll commit that shortly.)

OK, please do.

I am also testing a minor cleanup:
https://80x24.org/spew/20181118081847.16293-1-e@80x24.org/raw
(but will probably be afk next 12 hours or so)

> I think thread-safety of postponed_job and supporting MJIT in
> forked Ruby process are independent issues, but maybe your
> "workqueue" will be helpful for forked child somehow?

Somewhat related.  We need to ensure a consistent state of the
queue (either postponed_job or workqueue).

Right now, we cannot guarantee a consistent state after forking;
either.

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