From: Rich Felker <dalias@libc.org>
To: Rabbitstack <rabbitstack7@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: setrlimit hangs the process
Date: Thu, 4 Oct 2018 11:53:02 -0400 [thread overview]
Message-ID: <20181004155302.GD17110@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAA3hR4eiFavgWwZpp7=1d5U8k82dTouCVSy8ybes=tMyaDCpdg@mail.gmail.com>
On Thu, Oct 04, 2018 at 05:41:52PM +0200, Rabbitstack wrote:
> Please use the following link to download strace since daemon is refusing
> to deliver the mail.
>
> https://www.dropbox.com/s/syhbzxvijf7s4v1/agent.strace?dl=0
Here is the bug:
6208 rt_sigprocmask(SIG_SETMASK, ~[HUP INT QUIT ILL TRAP ABRT BUS FPE SEGV TERM STKFLT CHLD PROF SYS RTMIN RT_1], <unfinished ...>
Apparently Go has its own version of sigfillset, rather than calling
the libc one, and it's hard-coded the glibc values for which signals
are reserved for the implementation (just RTMIN and RT_1) rather than
honoring SIGRTMIN (which resolves at runtime via a function call),
which would exempt RT_2 from being blocked too.
It needs to be fixed on the Go side. I'll look at it later if nobody
else more familiar with Go gets to it sooner.
Rich
next prev parent reply other threads:[~2018-10-04 15:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 12:59 Rabbitstack
2018-09-25 14:15 ` Szabolcs Nagy
2018-09-25 14:54 ` Rabbitstack
2018-09-25 15:13 ` Rich Felker
2018-09-25 15:38 ` Szabolcs Nagy
2018-09-25 15:36 ` Szabolcs Nagy
2018-09-25 16:38 ` Rich Felker
2018-10-04 14:54 ` Rabbitstack
2018-10-04 15:04 ` Rich Felker
2018-10-04 15:41 ` Rabbitstack
2018-10-04 15:53 ` Rich Felker [this message]
2018-10-04 16:05 ` Rabbitstack
2018-10-05 0:47 ` Rich Felker
2018-10-09 19:37 ` Rabbitstack
2018-10-09 19:45 ` Rich Felker
2018-10-09 20:36 ` Szabolcs Nagy
2018-10-09 20:40 ` Rich Felker
2018-10-11 15:14 ` Rabbitstack
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=20181004155302.GD17110@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=rabbitstack7@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).