Linux Test Project
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
To: ltp@lists.linux.it
Subject: [LTP] [EXT] Re: [PATCH v9 00/24] ILP32 for ARM64
Date: Tue, 14 May 2019 16:41:49 -0700	[thread overview]
Message-ID: <20190514234149.GA12077@yury-thinkpad> (raw)
In-Reply-To: <20190514104311.GA24708@rei>

On Tue, May 14, 2019 at 12:43:11PM +0200, Cyril Hrubis wrote:
> Hi!
> > > There is a problem with the stack size accounting during execve when
> > > there is no stack limit:
> > >
> > > $ ulimit -s
> > > 8192
> > > $ ./hello.ilp32 
> > > Hello World!
> > > $ ulimit -s unlimited
> > > $ ./hello.ilp32 
> > > Segmentation fault
> > > $ strace ./hello.ilp32 
> > > execve("./hello.ilp32", ["./hello.ilp32"], 0xfffff10548f0 /* 77 vars */) = -1 ENOMEM (Cannot allocate memory)
> > > +++ killed by SIGSEGV +++
> > > Segmentation fault (core dumped)
> > >
> > > Andreas.
> > 
> > Thanks Andreas, I will take a look. Do we have such test in LTP?
> 
> We do have a test that we can run a binary with very small stack size
> i.e. 512kB but there does not seem to be anything that would catch this
> specific problem.
> 
> Can you please open an issue and describe how to reproduce the problem
> at our github tracker:
> 
> https://github.com/linux-test-project/ltp/issues
> 
> Then we can create testcase based on that reproducer later on.

This is it:
https://github.com/linux-test-project/ltp/issues/530

Yury

      parent reply	other threads:[~2019-05-14 23:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180516081910.10067-1-ynorov@caviumnetworks.com>
     [not found] ` <20190508225900.GA14091@yury-thinkpad>
     [not found]   ` <mvmtvdyoi33.fsf@suse.de>
2019-05-13 20:16     ` [LTP] [EXT] Re: [PATCH v9 00/24] ILP32 for ARM64 Yuri Norov
2019-05-14 10:43       ` Cyril Hrubis
2019-05-14 23:01         ` Yury Norov
2019-05-14 23:41         ` Yury Norov [this message]

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=20190514234149.GA12077@yury-thinkpad \
    --to=yury.norov@gmail.com \
    --cc=ltp@lists.linux.it \
    /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