From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] oom: fix oom04/5 Warning
Date: Tue, 10 Oct 2017 15:56:56 +0800 [thread overview]
Message-ID: <20171010075656.18796-1-liwang@redhat.com> (raw)
To get rid of the warnings, do nothing in cleanup() if NUMA node is less than 1.
oom04.c:61: CONF: requires NUMA with at least 1 node
mem.c:854: INFO: set overcommit_memory to 0
mem.c:761: WARN: open /dev/cpuset/tasks: ENOENT
mem.c:766: WARN: fopen /dev/cpuset/1/tasks: ENOENT
mem.c:778: WARN: rmdir /dev/cpuset/1: ENOENT
mem.c:780: WARN: umount /dev/cpuset: ENOENT
mem.c:782: WARN: rmdir /dev/cpuset: ENOENT
oom05.c:84: CONF: requires NUMA with at least 1 node
mem.c:854: INFO: set overcommit_memory to 0
mem.c:761: WARN: open /dev/cpuset/tasks: ENOENT
mem.c:766: WARN: fopen /dev/cpuset/1/tasks: ENOENT
mem.c:778: WARN: rmdir /dev/cpuset/1: ENOENT
mem.c:780: WARN: umount /dev/cpuset: ENOENT
mem.c:782: WARN: rmdir /dev/cpuset: ENOENT
mem.c:761: WARN: open /dev/cgroup/tasks: ENOENT
mem.c:766: WARN: fopen /dev/cgroup/1/tasks: ENOENT
mem.c:778: WARN: rmdir /dev/cgroup/1: ENOENT
mem.c:780: WARN: umount /dev/cgroup: ENOENT
mem.c:782: WARN: rmdir /dev/cgroup: ENOENT
Signed-off-by: Li Wang <liwang@redhat.com>
---
testcases/kernel/mem/oom/oom04.c | 3 +++
testcases/kernel/mem/oom/oom05.c | 3 +++
2 files changed, 6 insertions(+)
diff --git a/testcases/kernel/mem/oom/oom04.c b/testcases/kernel/mem/oom/oom04.c
index e4e70e2..6da690a 100644
--- a/testcases/kernel/mem/oom/oom04.c
+++ b/testcases/kernel/mem/oom/oom04.c
@@ -80,6 +80,9 @@ static void setup(void)
static void cleanup(void)
{
+ if (!is_numa(NULL, NH_MEMS, 1))
+ return;
+
set_sys_tune("overcommit_memory", overcommit, 0);
umount_mem(CPATH, CPATH_NEW);
}
diff --git a/testcases/kernel/mem/oom/oom05.c b/testcases/kernel/mem/oom/oom05.c
index bdf5d19..d874cc5 100644
--- a/testcases/kernel/mem/oom/oom05.c
+++ b/testcases/kernel/mem/oom/oom05.c
@@ -105,6 +105,9 @@ void setup(void)
void cleanup(void)
{
+ if (!is_numa(NULL, NH_MEMS, 1))
+ return;
+
set_sys_tune("overcommit_memory", overcommit, 0);
umount_mem(CPATH, CPATH_NEW);
umount_mem(MEMCG_PATH, MEMCG_PATH_NEW);
--
2.9.3
reply other threads:[~2017-10-10 7:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171010075656.18796-1-liwang@redhat.com \
--to=liwang@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