From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] mem/oom: fork may fail before test
Date: Mon, 23 May 2016 10:59:42 -0400 (EDT) [thread overview]
Message-ID: <629001822.73045.1464015582893.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20160523143611.GD25488@rei.lan>
----- Original Message -----
> From: "Cyril Hrubis" <chrubis@suse.cz>
> To: "Jan Stancek" <jstancek@redhat.com>
> Cc: ltp@lists.linux.it
> Sent: Monday, 23 May, 2016 4:36:11 PM
> Subject: Re: [LTP] [PATCH] mem/oom: fork may fail before test
>
> Hi!
> > On systems with small RAM and vm.overcommit_memory == 2,
> > the system may already be in state where Committed_AS is
> > larger than CommitLimit due to various backround daemons
> > (NM, tuned, polkitd,...) asking for big allocations.
> >
> > In such instances oom testcases report TBROK on very first fork.
> > This patch allows this to be a valid outcome (TPASS).
>
> Looks good to me, acked.
Pushed.
Regards,
Jan
>
> --
> Cyril Hrubis
> chrubis@suse.cz
>
prev parent reply other threads:[~2016-05-23 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 14:58 [LTP] [PATCH] mem/oom: fork may fail before test Jan Stancek
2016-05-23 14:36 ` Cyril Hrubis
2016-05-23 14:59 ` Jan Stancek [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=629001822.73045.1464015582893.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.