public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/setrlimit: add setrlimit04
Date: Mon, 17 Jul 2017 05:43:19 -0400 (EDT)	[thread overview]
Message-ID: <1856940022.53375066.1500284599278.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAEemH2dznQRLRdKAL4HOR49WBDahB8WSXVLCGwgZNyFu22r0hA@mail.gmail.com>



----- Original Message -----
> On Mon, Jul 17, 2017 at 2:50 PM, Jan Stancek <jstancek@redhat.com> wrote:
> >
> >
> > ----- Original Message -----
> >> On Fri, Jul 14, 2017 at 7:12 PM, Jan Stancek <jstancek@redhat.com> wrote:
> >> > Early patches for stack guard gap caused that gap size was contributing
> >> > towards stack limit. This caused failures for new processes (E2BIG) when
> >> > ulimit was set to anything lower than size of gap.
> > ...
> >> > +static struct tst_test test = {
> >> > +       .test_all     = test_setrlimit,
> >> > +       .forks_child  = 1,
> >> > +       .needs_root = 1,
> >>
> >> seems we need to filter out the suitable kernel:
> >>
> >> .min_kver = "4.12.0",
> >
> > Why, shouldn't this work on any kernel version?
> 
> My bad. The "Early patches" has been reverted. I mistook this issue in
> versions.
> 
> You are right. please ignore my comments in last mail. :)
> 
> 
> Another question come to my mind is that, if a system reboot with
> kernel parameter "stack_guard_gap=xxx", this case setrlimit04 still
> runs well and getting PASS, right?

Yes.

On side note, I also want a testcase in LTP where we on purpose keep
expanding stack until it hits existing mapping. 

  reply	other threads:[~2017-07-17  9:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 11:12 [LTP] [PATCH] syscalls/setrlimit: add setrlimit04 Jan Stancek
2017-07-14 12:45 ` Richard Palethorpe
2017-07-17  7:01   ` Jan Stancek
2017-07-17  5:01 ` Li Wang
2017-07-17  6:50   ` Jan Stancek
2017-07-17  7:50     ` Li Wang
2017-07-17  9:43       ` Jan Stancek [this message]
2017-10-02 13:11 ` Cyril Hrubis
2017-10-02 13:55   ` Jan Stancek

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=1856940022.53375066.1500284599278.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.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