From: Dong ZHu <bluezhudong@gmail.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH V2] controllers/memcg: Mark testcase_2 as pass when mlock failed
Date: Thu, 2 Jun 2016 09:36:57 +0800 [thread overview]
Message-ID: <20160602013657.GA8737@localhost.localdomain> (raw)
In-Reply-To: <20160601093652.GB19762@rei.lan>
On Wed, Jun 01, 2016 at 11:36:52AM +0200, Cyril Hrubis wrote:
> Hi!
> This one is much better but not yet 100% right. Comments below.
Thanks for your suggestion.
> Please use tabs only for the indentation. This code mixes tabs and
> spaces.
Fixed it.
>
> Also I think that it would be far better if we do just exit(2) here and
> print somehing as "Failed to allocate/lock/populate memory" from
> memcg_lib.sh if the memcg_process.c exits with 2 in the test_proc_kill().
I think we should make a judgment of the return value of mlock, because
only EAGAIN is expected.
Below is the patch:
--8<--
While running "memcg_memsw_limit_in_bytes_test" always reported below error:
"memcg_memsw_limit_in_bytes_test 2 TFAIL : ltpapicmd.c:193: process 3769
is killed by error"
In function mmap_lock2() mlock failed to lock pages with errno EAGAIN,
the "memcg_process" process exit not the oom killer kill it.
Base on the this:
http://marc.info/?l=linux-mm&m=142122902313315&w=2
So mlock failed it is a expect behavior, in this case test should return
PASS.
Signed-off-by: Dong Zhu <bluezhudong@gmail.com>
---
testcases/kernel/controllers/memcg/functional/memcg_lib.sh | 5 ++++-
testcases/kernel/controllers/memcg/functional/memcg_process.c | 8 ++++++--
2 files changed, 10 insertions(+), 3 deletions(-)
diff --git a/testcases/kernel/controllers/memcg/functional/memcg_lib.sh b/testcases/kernel/controllers/memcg/functional/memcg_lib.sh
index 9b9b0fd..b0dfce0 100755
--- a/testcases/kernel/controllers/memcg/functional/memcg_lib.sh
+++ b/testcases/kernel/controllers/memcg/functional/memcg_lib.sh
@@ -229,8 +229,11 @@ test_proc_kill()
ps -p $pid > /dev/null 2> /dev/null
if [ $? -ne 0 ]; then
wait $pid
- if [ $? -eq 1 ]; then
+ ret=$?
+ if [ $ret -eq 1 ]; then
result $FAIL "process $pid is killed by error"
+ elif [[ $ret -eq 2 ]]; then
+ result $PASS "Failed to lock memory"
else
result $PASS "process $pid is killed"
fi
diff --git a/testcases/kernel/controllers/memcg/functional/memcg_process.c b/testcases/kernel/controllers/memcg/functional/memcg_process.c
index 3d34394..40c677b 100644
--- a/testcases/kernel/controllers/memcg/functional/memcg_process.c
+++ b/testcases/kernel/controllers/memcg/functional/memcg_process.c
@@ -203,8 +203,12 @@ void mmap_lock2()
if (p == MAP_FAILED)
err(1, "mmap failed");
- if (mlock(p, memsize) == -1)
- err(1, "mlock failed");
+ if (mlock(p, memsize) == -1) {
+ if (errno == EAGAIN)
+ exit(2);
+ else
+ err(1, "mlock failed");
+ }
} else {
if (munmap(p, memsize) == -1)
err(1, "munmap failed");
--
2.1.0
--
Best Regards,
Dong Zhu
next prev parent reply other threads:[~2016-06-02 1:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 3:00 [LTP] [PATCH] controllers/memcg: Mark testcase_2 as pass when mlock failed Dong ZHu
2016-06-01 9:07 ` [LTP] [Re-Send][PATCH] " Dong ZHu
2016-06-01 9:36 ` Cyril Hrubis
2016-06-02 1:36 ` Dong ZHu [this message]
2016-06-06 1:20 ` [LTP] [PATCH V2] " Dong ZHu
2016-06-06 13:16 ` Cyril Hrubis
2016-06-07 1:44 ` [LTP] [PATCH V3] " Dong ZHu
2016-06-07 10:45 ` Cyril Hrubis
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=20160602013657.GA8737@localhost.localdomain \
--to=bluezhudong@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