From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Cc: Rabbitstack <rabbitstack7@gmail.com>
Subject: Re: setrlimit hangs the process
Date: Tue, 9 Oct 2018 16:40:03 -0400 [thread overview]
Message-ID: <20181009204003.GK17110@brightrain.aerifal.cx> (raw)
In-Reply-To: <20181009203640.GS10209@port70.net>
On Tue, Oct 09, 2018 at 10:36:41PM +0200, Szabolcs Nagy wrote:
> * Rabbitstack <rabbitstack7@gmail.com> [2018-10-09 21:37:06 +0200]:
> > Should we raise an issue in Go upstream repository since there is nothing
> > actionable from musl side?
> >
>
> have you figured out where the siprocmask came from?
> it might not be the go runtime but some c lib that you linked in.
Well the sigset_t was created in Go code or via some other code that
bypasses libc. The libc functions cannot create a sigset_t with the
implementation-internal signals masked.
> > El vie., 5 oct. 2018 2:47, Rich Felker <dalias@libc.org> escribió:
> > > >
> > > > 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 ...>
>
> the go runtime should not make this call, it probably comes from
> somewhere else.
>
> i think you should try to create a minimal reproducer go code
> that makes this syscall.
I looked at the Go implementations of the functions for sigset_t
manipulation and sigprocmask. They all bypass libc. So either it's an
error to use them at all in programs that link with libc, or a bug in
Go that they don't respect SIGRTMIN, etc.
Rich
next prev parent reply other threads:[~2018-10-09 20:40 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
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 [this message]
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=20181009204003.GK17110@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).