From: Eric Wong <e@80x24.org>
To: spew@80x24.org
Subject: [PATCH 13/14] signal.c: prevent spurious wakeup of main thread for SIGCHLD
Date: Tue, 26 Jun 2018 09:38:16 +0000 [thread overview]
Message-ID: <20180626093817.1533-14-e@80x24.org> (raw)
In-Reply-To: <20180626093817.1533-1-e@80x24.org>
This is necessary for test/-ext-/gvl/test_last_thread.rb to
pass with MJIT enabled, as that test fails if spurious wakeup
happens.
---
signal.c | 40 ++++++++++++++++++++++------------------
1 file changed, 22 insertions(+), 18 deletions(-)
diff --git a/signal.c b/signal.c
index d09480fb6f..90d7824b2b 100644
--- a/signal.c
+++ b/signal.c
@@ -692,12 +692,29 @@ signal_enque(int sig)
ATOMIC_INC(signal_buff.size);
}
+static sig_atomic_t sigchld_hit;
+
+/* Prevent compiler from reordering access */
+#define ACCESS_ONCE(type,x) (*((volatile type *)&(x)))
+
static RETSIGTYPE
sighandler(int sig)
{
int old_errnum = errno;
- signal_enque(sig);
+ /* the VM always needs to handle SIGCHLD for rb_waitpid */
+ if (sig == RUBY_SIGCHLD) {
+ rb_vm_t *vm = GET_VM();
+ sigchld_hit = 1;
+
+ /* avoid spurious wakeup in main thread iff nobody uses trap(:CHLD) */
+ if (vm && ACCESS_ONCE(VALUE, vm->trap_list.cmd[sig])) {
+ signal_enque(sig);
+ }
+ }
+ else {
+ signal_enque(sig);
+ }
rb_thread_wakeup_timer_thread();
#if !defined(BSD_SIGNAL) && !defined(POSIX_SIGNAL)
ruby_signal(sig, sighandler);
@@ -1048,13 +1065,8 @@ void ruby_waitpid_all(rb_vm_t *); /* process.c */
void
ruby_sigchld_handler(rb_vm_t *vm)
{
- /*
- * Checking signal_buff.cnt[RUBY_SIGCHLD] here is not completely
- * reliable as it can race with rb_get_next_signal in the
- * main thread. However, this remains useful when the main thread
- * is blocked in an uninterruptible state:
- */
- if (signal_buff.cnt[RUBY_SIGCHLD]) {
+ if (sigchld_hit) {
+ sigchld_hit = 0;
ruby_waitpid_all(vm);
}
}
@@ -1066,14 +1078,6 @@ rb_signal_exec(rb_thread_t *th, int sig)
VALUE cmd = vm->trap_list.cmd[sig];
int safe = vm->trap_list.safe[sig];
- /*
- * This is necessary as rb_get_next_signal from this (main) thread
- * can steal work from the timer-thread running ruby_sigchld_handler
- */
- if (RUBY_SIGCHLD == sig) {
- ruby_waitpid_all(vm);
- }
-
if (cmd == 0) {
switch (sig) {
case SIGINT:
@@ -1295,7 +1299,7 @@ trap(int sig, sighandler_t func, VALUE command)
break;
}
- vm->trap_list.cmd[sig] = command;
+ ACCESS_ONCE(VALUE, vm->trap_list.cmd[sig]) = command;
vm->trap_list.safe[sig] = rb_safe_level();
return oldcmd;
@@ -1450,7 +1454,7 @@ init_sigchld(int sig)
oldfunc = ruby_signal(sig, SIG_DFL);
if (oldfunc == SIG_ERR) return -1;
ruby_signal(sig, func);
- GET_VM()->trap_list.cmd[sig] = 0;
+ ACCESS_ONCE(VALUE, GET_VM()->trap_list.cmd[sig]) = 0;
return 0;
}
--
EW
next prev parent reply other threads:[~2018-06-26 9:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 9:38 [PATCH 00/14] SIGCHLD hijack for waitpid Eric Wong
2018-06-26 9:38 ` [PATCH 01/14] hijack SIGCHLD handler for internal use Eric Wong
2018-06-26 9:38 ` [PATCH 02/14] fix SIGCHLD hijacking race conditions Eric Wong
2018-06-26 9:38 ` [PATCH 03/14] mjit.c: allow working on platforms without SIGCHLD Eric Wong
2018-06-26 9:38 ` [PATCH 04/14] cleanups Eric Wong
2018-06-26 9:38 ` [PATCH 05/14] handle SIGCHLD in both the timer-thread and main thread Eric Wong
2018-06-26 9:38 ` [PATCH 06/14] Revert "test_process.rb: skip tests for Bug 14867" Eric Wong
2018-06-26 9:38 ` [PATCH 07/14] Revert "spec: skip Process wait specs on MJIT" Eric Wong
2018-06-26 9:38 ` [PATCH 08/14] wip testing Eric Wong
2018-06-26 9:38 ` [PATCH 09/14] pgrp list Eric Wong
2018-06-26 9:38 ` [PATCH 10/14] grantpt Eric Wong
2018-06-26 9:38 ` [PATCH 11/14] blocking mjit_finish Eric Wong
2018-06-26 9:38 ` [PATCH 12/14] reinitialize waitpid_lock Eric Wong
2018-06-26 9:38 ` Eric Wong [this message]
2018-06-26 9:38 ` [PATCH 14/14] process.c (rb_waitpid): reimplement non-SIGCHLD code path Eric Wong
2018-06-26 10:51 ` [PATCH 15/14] force SIGCHLD to the timer-thread Eric Wong
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=20180626093817.1533-14-e@80x24.org \
--to=e@80x24.org \
--cc=spew@80x24.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).