ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "alexdowad (Alex Dowad) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "alexdowad (Alex Dowad)" <noreply@ruby-lang.org>
Subject: [ruby-core:113782] [Ruby master Bug#19716] SystemStackError occurs too easily on Alpine Linux (due to small stack size reported by pthread_attr_getstacksize on musl libc)
Date: Wed, 07 Jun 2023 00:13:59 +0000 (UTC)	[thread overview]
Message-ID: <redmine.issue-19716.20230607001359.5454@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-19716.20230607001359.5454@ruby-lang.org

Issue #19716 has been reported by alexdowad (Alex Dowad).

----------------------------------------
Bug #19716: SystemStackError occurs too easily on Alpine Linux (due to small stack size reported by pthread_attr_getstacksize on musl libc)
https://bugs.ruby-lang.org/issues/19716

* Author: alexdowad (Alex Dowad)
* Status: Open
* Priority: Normal
* ruby -v: ruby 3.1.4p223 (2023-03-30 revision 957bb7cb81) [x86_64-linux-musl]
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN
----------------------------------------
This is the same problem previously reported against Ruby 2.5 in https://bugs.ruby-lang.org/issues/14387. I just ran into the same problem on Ruby 3.1.4, built on Alpine Linux 3.16.

@hsbt stated in the previous thread (https://bugs.ruby-lang.org/issues/14387#note-28):

> If you have this issue with Ruby 3.2, please file it with another issue.

I hacked `stack_check` in gc.c to print the values of `STACK_START` and `STACK_END` on stack overflow; on the Alpine 3.16 host where this problem just occurred, the values printed were:

> Start=0x7ffd0bf4f000, End=0x7ffd0bf32530

...which shows that Ruby thinks the stack size is only 131072 bytes. On the other hand, `ulimit -s` shows a stack size limit of 8192kb.

This Ruby 3.1.4 was built from unmodified source code downloaded from https://cache.ruby-lang.org; the build was configured using `CFLAGS='-march=native' ./configure --disable-install-doc`.

The invocation of Ruby which blew the stack was `bundle exec rake db:migrate`, on a mid-sized Rails project.

Regarding @ncopa's patch from #14387, @wanabe listed some things which should be done before it is merged into mainline Ruby:

> Okay, The patch needs one or more proofs of its behaviour, like that:
> 
> Original issue [ruby-dev:50421] has gone away.
> Standard test codes run well.
> test-all
> ruby/spec
> getrlimit works on some situations like:
> on single thread
> with multiple threads
> with RLIMIT_STACK environment variable
> getrlimit code of musl is implemented correctly as expected.
> (But It's doubtful whether it can be. I guess that a proof of code soundness is very difficult.)
> Some "real world" applications can work.
> I think it is better example that that application(s) can't work without the patch.

I am happy to help cover some of these points if the Ruby development team is still interested in merging @ncopa's patch.



-- 
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/postorius/lists/ruby-core.ml.ruby-lang.org/

       reply	other threads:[~2023-06-07  0:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07  0:13 alexdowad (Alex Dowad) via ruby-core [this message]
2023-06-07  0:19 ` [ruby-core:113783] [Ruby master Bug#19716] SystemStackError occurs too easily on Alpine Linux (due to small stack size reported by pthread_attr_getstacksize on musl libc) alexdowad (Alex Dowad) via ruby-core
2023-06-07  0:27 ` [ruby-core:113784] " alexdowad (Alex Dowad) via ruby-core
2023-11-12  0:53 ` [ruby-core:115347] " retro via ruby-core
2024-03-27  1:03 ` [ruby-core:117335] " hsbt (Hiroshi SHIBATA) via ruby-core
2024-03-27 11:48 ` [ruby-core:117344] " ncopa (Natanael Copa) 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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.issue-19716.20230607001359.5454@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    --cc=noreply@ruby-lang.org \
    --cc=ruby-core@ml.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 read-only IMAP folder(s) and NNTP newsgroup(s).