[#85349] [Ruby trunk Bug#14334] Segmentation fault after running rspec (ruby/2.5.0/erb.rb:885 / simplecov/source_file.rb:85) — pragtob@...
Issue #14334 has been updated by PragTob (Tobias Pfeiffer).
3 messages
2018/02/02
[#85358] Re: [ruby-cvs:69220] nobu:r62039 (trunk): compile.c: unnecessary freezing — Eric Wong <normalperson@...>
[email protected] wrote:
5 messages
2018/02/03
[#85612] Why require autoconf 2.67+ — leam hall <leamhall@...>
Please pardon the intrusion; I am new to Ruby and like to pull the
6 messages
2018/02/17
[#85616] Re: Why require autoconf 2.67+
— Vít Ondruch <v.ondruch@...>
2018/02/18
VGhpcyBjb3VsZCBoZWxwIHlvdSB0byBidWlsZCBSdWJ5IHdpdGggb2xkZXIgYXV0b2NvbmYgKDIu
[#85634] [Ruby trunk Bug#14494] [PATCH] tool/m4/ruby_replace_type.m4 use AC_CHECK_TYPES for HAVE_* macros — normalperson@...
Issue #14494 has been reported by normalperson (Eric Wong).
3 messages
2018/02/19
[#85674] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — matz@...
Issue #13618 has been updated by matz (Yukihiro Matsumoto).
5 messages
2018/02/20
[#85686] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/02/20
[email protected] wrote:
[#85704] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Koichi Sasada <ko1@...>
2018/02/21
On 2018/02/20 18:06, Eric Wong wrote:
[ruby-core:85529] Re: [Ruby trunk Bug#14357] thread_safe tests suite segfaults
From:
Vladimir Makarov <vmakarov@...>
Date:
2018-02-13 21:31:34 UTC
List:
ruby-core #85529
On 02/13/2018 05:13 AM, Eric Wong wrote: > [email protected] wrote: >> File thread-table-rebuild.patch added > Thank you for working on this! > >> This problem results in ICE for new hash tables. For old hash >> tables, the problem would have corrupted hash table structure which >> probably results in later incorrect table behaviour. > ICE - Internal Compiler Error? Or did you mean "use-after-free"? Fortunately, not internal compiler error (i wrongly used the term from GCC development :). I meant use-after-free. > Yes, 2.3 and earlier st.c is affected by this, too, just seems > to hit less frequently... 2.3 maintainer(s) will need to > backport from scratch, maybe > > <snip> > > I have no write access to Ruby repository. So please, consider the <snip> >> I cannot find where changelog entry should go for the current trunk, >> but here it is. > We write changelog entries in the commit message nowadays. In the > future, you can send the output of "git format-patch" since it > appears you're using git anyways and we can "git am" it. > > I also wrote the following text to summarize in r62396 > > st.c: retry operations if rebuilt > > Calling the .eql? and .hash methods during a Hash operation can > result in a thread switch or a signal handler to run: allowing > one execution context to rebuild the hash table while another is > still reading or writing the table. This results in a > use-after-free bug affecting the thread_safe-0.3.6 test suite > and likely other bugs. > > This bug did not affect users of commonly keys (String, Symbol, > Fixnum) as those are optimized to avoid method dispatch > for .eql? and .hash methods. > > A separate version of this change needs to be ported to Ruby 2.3.x > which had a different implementation of st.c but was affected > by the same bug. > > (and copied your changelog entry below) Thank you, Eric! Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
