General

Profile

dugg (Doug E)

  • Login: dugg
  • Registered on: 10/05/2026
  • Last sign in: 10/05/2026

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 0 0 0

Activity

10/17/2026

11:37 AM Ruby Revision 50f66248 (git): Reset the fork lock in the child without unlocking it
A thread that is waiting for the fork lock when another thread forks
exists only in the parent, but on macOS the child's copy of the lock
still counts it. After the child unlocks its copy,
pthread_rwlock_destroy() and pthread_rwlock_init...
dugg (Doug E)
05:24 AM Ruby Revision 56c3e7ea (git): Join getaddrinfo and getnameinfo threads before fork
A getaddrinfo thread calls getaddrinfo(3) inside rb_thread_prevent_fork,
but on glibc its thread exit takes the resolver configuration lock again
after the thread has released the fork lock. A fork that lands then
leaves the child with t...
dugg (Doug E)

10/15/2026

07:37 PM Ruby Revision 27204205 (git): Reset the fork lock in the child without unlocking it
A thread that is waiting for the fork lock when another thread forks
exists only in the parent, but on macOS the child's copy of the lock
still counts it. After the child unlocks its copy,
pthread_rwlock_destroy() and pthread_rwlock_init...
dugg (Doug E)
06:23 PM Ruby Bug #22445 (Closed): On macOS, a child of Kernel#fork can abort with "[BUG] pthread_rwlock_destroy: Resource busy (EBUSY)"
Applied in changeset commit:git|e06b9da3f20455ba4cff99a7821f013b7bdde5de.
----------
Reset the fork lock in the child without unlocking it
A thread that is waiting for the fork lock when another thread forks
exists only in the parent, ...
dugg (Doug E)
06:23 PM Ruby Revision e06b9da3 (git): Reset the fork lock in the child without unlocking it
A thread that is waiting for the fork lock when another thread forks
exists only in the parent, but on macOS the child's copy of the lock
still counts it. After the child unlocks its copy,
pthread_rwlock_destroy() and pthread_rwlock_init...
dugg (Doug E)
12:15 AM Ruby Revision 59db3a3a (git): Join getaddrinfo and getnameinfo threads before fork
A getaddrinfo thread calls getaddrinfo(3) inside rb_thread_prevent_fork,
but on glibc its thread exit takes the resolver configuration lock again
after the thread has released the fork lock. A fork that lands then
leaves the child with t...
dugg (Doug E)

10/14/2026

08:46 AM Ruby Bug #22406 (Closed): Process.fork can leave the child unable to resolve hostnames: getaddrinfo helper threads take glibc's resolver lock after releasing the fork lock
Applied in changeset commit:git|44f7c6b00d3263c9c81af58e77eeb79eaec7bd0e.
----------
Join getaddrinfo and getnameinfo threads before fork
A getaddrinfo thread calls getaddrinfo(3) inside rb_thread_prevent_fork,
but on glibc its thread ...
dugg (Doug E)
08:46 AM Ruby Revision 44f7c6b0 (git): Join getaddrinfo and getnameinfo threads before fork
A getaddrinfo thread calls getaddrinfo(3) inside rb_thread_prevent_fork,
but on glibc its thread exit takes the resolver configuration lock again
after the thread has released the fork lock. A fork that lands then
leaves the child with t...
dugg (Doug E)

Also available in: Atom