From: usa@garbagecollect.jp
To: ruby-core@ruby-lang.org
Subject: [ruby-core:91360] [Ruby trunk Bug#15041] [PATCH] cont.c: set th->root_fiber to current fiber at fork
Date: Thu, 31 Jan 2019 11:02:57 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-76613.20190131110255.55c802e08fc27069@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15041.20180829065903@ruby-lang.org
Issue #15041 has been updated by usa (Usaku NAKAMURA).
Backport changed from 2.3: REQUIRED, 2.4: REQUIRED, 2.5: DONE to 2.3: REQUIRED, 2.4: DONE, 2.5: DONE
ruby_2_4 r66968 merged revision(s) 64589,64593.
----------------------------------------
Bug #15041: [PATCH] cont.c: set th->root_fiber to current fiber at fork
https://bugs.ruby-lang.org/issues/15041#change-76613
* Author: normalperson (Eric Wong)
* Status: Closed
* Priority: Normal
* Assignee:
* Target version:
* ruby -v:
* Backport: 2.3: REQUIRED, 2.4: DONE, 2.5: DONE
----------------------------------------
cont.c: set th->root_fiber to current fiber at fork
Otherwise, th->root_fiber can point to an invalid Fiber,
because Fibers do not live across fork. So consider
whatever Fiber is running the root fiber.
---Files--------------------------------
0001-cont.c-set-th-root_fiber-to-current-fiber-at-fork.patch (2.13 KB)
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2019-01-31 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15041.20180829065903@ruby-lang.org>
2018-08-29 6:59 ` [ruby-core:88722] [Ruby trunk Bug#15041] [PATCH] cont.c: set th->root_fiber to current fiber at fork normalperson
2018-08-29 7:20 ` [ruby-core:88723] " ko1
2018-08-29 8:09 ` [ruby-core:88724] " Eric Wong
2018-08-30 6:34 ` [ruby-core:88744] " Koichi Sasada
2019-01-14 9:23 ` [ruby-core:91073] " nagachika00
2019-01-31 11:02 ` usa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-76613.20190131110255.55c802e08fc27069@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).