linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: ltp@lists.linux.it, linux-mm@kvack.org
Cc: open list <linux-kernel@vger.kernel.org>,
	Jan Stancek <jstancek@redhat.com>,
	 lkft-triage@lists.linaro.org, dengke.du@windriver.com,
	petr.vorel@gmail.com
Subject: LTP: mm: overcommit_memory01, 03...06 failed
Date: Wed, 15 May 2019 14:10:43 +0530	[thread overview]
Message-ID: <CA+G9fYu254sYc77jOVifOmxrd_jNmr4wNHTrqnW54a8F=EQZ6Q@mail.gmail.com> (raw)

ltp-mm-tests failed on Linux mainline kernel  5.1.0,
  * overcommit_memory01 overcommit_memory
  * overcommit_memory03 overcommit_memory -R 30
  * overcommit_memory04 overcommit_memory -R 80
  * overcommit_memory05 overcommit_memory -R 100
  * overcommit_memory06 overcommit_memory -R 200

mem.c:814: INFO: set overcommit_memory to 0
overcommit_memory.c:185: INFO: malloc 8094844 kB successfully
overcommit_memory.c:204: PASS: alloc passed as expected
overcommit_memory.c:189: INFO: malloc 32379376 kB failed
overcommit_memory.c:210: PASS: alloc failed as expected
overcommit_memory.c:185: INFO: malloc 16360216 kB successfully
overcommit_memory.c:212: FAIL: alloc passed, expected to fail

Failed test log,
https://lkft.validation.linaro.org/scheduler/job/726417#L22852

LTP version 20190115

Test case link,
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/mem/tunable/overcommit_memory.c#L212

First bad commit:
git branch master
git commit e0654264c4806dc436b291294a0fbf9be7571ab6
git describe v5.1-10706-ge0654264c480
git repo https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

Last good commit:
git branch master
git commit 7e9890a3500d95c01511a4c45b7e7192dfa47ae2
git describe v5.1-10326-g7e9890a3500d
git repo https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

Best regards
Naresh Kamboju


             reply	other threads:[~2019-05-15  8:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15  8:40 Naresh Kamboju [this message]
2019-05-15  9:03 ` 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='CA+G9fYu254sYc77jOVifOmxrd_jNmr4wNHTrqnW54a8F=EQZ6Q@mail.gmail.com' \
    --to=naresh.kamboju@linaro.org \
    --cc=dengke.du@windriver.com \
    --cc=jstancek@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=ltp@lists.linux.it \
    --cc=petr.vorel@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox