From: "nagachika (Tomoyuki Chikanaga)" <noreply@...>
Date: 2022-11-13T02:23:55+00:00
Subject: [ruby-core:110732] [Ruby master Bug#19105] mutex: Raise a ThreadError when detecting a fiber deadlock

Issue #19105 has been updated by nagachika (Tomoyuki Chikanaga).

Backport changed from 2.7: DONTNEED, 3.0: REQUIRED, 3.1: REQUIRED to 2.7: DONTNEED, 3.0: REQUIRED, 3.1: DONE

ruby_3_1 61818395312c6e765dc8e7be8bf32cd2c82fec39 merged revision(s) eacedcfe44a0ae22bf54ddb7df193c48d4c857c6.

----------------------------------------
Bug #19105: mutex: Raise a ThreadError when detecting a fiber deadlock
https://bugs.ruby-lang.org/issues/19105#change-100067

* Author: byroot (Jean Boussier)
* Status: Closed
* Priority: Normal
* Backport: 2.7: DONTNEED, 3.0: REQUIRED, 3.1: DONE
----------------------------------------
The following code can lead to a deadlock but not raise any error:

```ruby
mutex = Mutex.new
mutex.synchronize do
  error = assert_raise ThreadError do
    Fiber.new do
      mutex.lock
    end.resume
  end
end
```

If no fiber scheduler is registered, and both the fiber that currently own the lock and the one trying to acquire it belongs to the same thread, then this deadlock situation cannot possibly resolve (aside from a signal interrupt maybe).

Discussed in https://bugs.ruby-lang.org/issues/17827#note-10
Pull request: https://github.com/ruby/ruby/pull/6680




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

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