From: "ioquatix (Samuel Williams) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "ioquatix (Samuel Williams)" <noreply@ruby-lang.org>
Subject: [ruby-core:120674] [Ruby master Bug#21038] Preserve `errno` in `rb_fiber_scheduler_unblock`
Date: Wed, 15 Jan 2025 00:39:52 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-21038.20250115003952.3344@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-21038.20250115003952.3344@ruby-lang.org>
Issue #21038 has been reported by ioquatix (Samuel Williams).
----------------------------------------
Bug #21038: Preserve `errno` in `rb_fiber_scheduler_unblock`
https://bugs.ruby-lang.org/issues/21038
* Author: ioquatix (Samuel Williams)
* Status: Open
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN
----------------------------------------
`rb_fiber_scheduler_unblock` can invoke user code that can affect `errno`, and at least in `io_binwrite`, this is unexpected. Whether `io_binwrite` should be fixed is a separate issue (it probably should be, as `errno` is not explicitly preserved or documented how it is preserved).
See <https://github.com/socketry/io-event/issues/127> for more discussion.
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/
next parent reply other threads:[~2025-01-15 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 0:39 ioquatix (Samuel Williams) via ruby-core [this message]
2025-01-15 5:13 ` [ruby-core:120692] " k0kubun (Takashi Kokubun) via ruby-core
2025-01-25 6:34 ` [ruby-core:120792] " nagachika (Tomoyuki Chikanaga) via ruby-core
2025-02-14 5:09 ` [ruby-core:121022] " k0kubun (Takashi Kokubun) via ruby-core
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-21038.20250115003952.3344@ruby-lang.org \
--to=ruby-core@ml.ruby-lang.org \
--cc=noreply@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 NNTP newsgroup(s).