mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Cc: Rabbitstack <rabbitstack7@gmail.com>
Subject: Re: setrlimit hangs the process
Date: Tue, 25 Sep 2018 17:38:13 +0200	[thread overview]
Message-ID: <20180925153813.GG10209@port70.net> (raw)
In-Reply-To: <20180925151336.GK17995@brightrain.aerifal.cx>

* Rich Felker <dalias@libc.org> [2018-09-25 11:13:36 -0400]:
> The trace here shows a thread, tid 9285, the main thread, not
> responding to the broadcast signals that are necessary to stop all
> threads for the purpose of changing resource limits, uids/gids/etc.

ah i didnt know this is used for setrlimit too.

that explains what goes wrong.

> I'm guessing some part of the Go runtime has bypassed libc and blocked
> libc-internal signals in the main thread. A full strace rather than a
> truncated one like the above would show this happening. If you can
> produce one that doesn't expose private data that would be helpful; if
> not, perhaps it's possible to write a minimal Go program that
> reproduces the issue and strace it instead.
> 
> Rich


  reply	other threads:[~2018-09-25 15:38 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 [this message]
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
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=20180925153813.GG10209@port70.net \
    --to=nsz@port70.net \
    --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).