From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: xiao yang <yangx.jy@cn.fujitsu.com>
Cc: fstests@vger.kernel.org, darrick.wong@oracle.com, eguan@redhat.com
Subject: Re: [PATCH v2] syscalls/madvise09.c: Use custom mount point instead of /sys/fs/cgroup/memory
Date: Fri, 12 Jan 2018 14:19:36 +0800 [thread overview]
Message-ID: <5A585378.70900@cn.fujitsu.com> (raw)
In-Reply-To: <1515737662-1993-1-git-send-email-yangx.jy@cn.fujitsu.com>
Hi,
Sorry, please ignore the wrong patchset, i will resend the v2 patchset.
Thanks,
Xiao Yang
On 2018/01/12 14:14, xiao yang wrote:
> 1) on some distros(e.g. RHEL6), memory cgroup was supported and
> mounted on /cgroup/memory by default, but the test was skipped
> if /sys/fs/cgroup/memory did not exist.
>
> 2) We got the following error if memory cgroup wasn't mounted
> on /sys/fs/cgroup/memory:
> ------------------------------------------------------------
> safe_macros.c:169: BROK: madvise09.c:175: mkdir(/sys/fs/cgroup/memory/ltp_madvise09_16386/,0777) failed: EROFS
> ------------------------------------------------------------
>
> We use custom mount point and mount memory cgroup on it manually
> to fix these issues.
>
> Signed-off-by: xiao yang <yangx.jy@cn.fujitsu.com>
> ---
> testcases/kernel/syscalls/madvise/madvise09.c | 26 ++++++++++++++++++++++----
> 1 file changed, 22 insertions(+), 4 deletions(-)
>
> diff --git a/testcases/kernel/syscalls/madvise/madvise09.c b/testcases/kernel/syscalls/madvise/madvise09.c
> index f744405..25cf81f 100644
> --- a/testcases/kernel/syscalls/madvise/madvise09.c
> +++ b/testcases/kernel/syscalls/madvise/madvise09.c
> @@ -53,12 +53,14 @@
> #include <errno.h>
> #include <stdio.h>
> #include <ctype.h>
> +#include <sys/mount.h>
>
> #include "tst_test.h"
> #include "lapi/mmap.h"
>
> -#define MEMCG_PATH "/sys/fs/cgroup/memory/"
> +#define MEMCG_PATH "/dev/memcg_madvise09/"
>
> +static int memcg_mounted;
> static char cgroup_path[PATH_MAX];
> static char tasks_path[PATH_MAX];
> static char limit_in_bytes_path[PATH_MAX];
> @@ -277,6 +279,15 @@ static void cleanup(void)
> {
> if (cgroup_path[0] && !access(cgroup_path, F_OK))
> rmdir(cgroup_path);
> +
> + if (memcg_mounted) {
> + tst_res(TINFO, "Umount memory cgroup after testing");
> + SAFE_UMOUNT(MEMCG_PATH);
> + memcg_mounted = 0;
> + }
> +
> + if (!access(MEMCG_PATH, F_OK) && rmdir(MEMCG_PATH))
> + tst_res(TWARN | TERRNO, "Rmdir %s failed", MEMCG_PATH);
> }
>
> static void run(void)
> @@ -316,10 +327,17 @@ static void setup(void)
> {
> long int swap_total;
>
> - if (access(MEMCG_PATH, F_OK)) {
> - tst_brk(TCONF, "'" MEMCG_PATH
> - "' not present, CONFIG_MEMCG missing?");
> + SAFE_MKDIR(MEMCG_PATH, 0777);
> +
> + tst_res(TINFO, "Mount memory cgroup on %s", MEMCG_PATH);
> + if (mount("memcg", MEMCG_PATH, "cgroup", 0, "memory") == -1) {
> + if (errno == ENODEV) {
> + tst_brk(TCONF,
> + "Memory cgroup was not configured in kernel");
> + }
> + tst_brk(TBROK | TERRNO, "Failed to mount memory cgroup");
> }
> + memcg_mounted = 1;
>
> if (!access(MEMCG_PATH "memory.memsw.limit_in_bytes", F_OK))
> swap_accounting_enabled = 1;
next prev parent reply other threads:[~2018-01-12 6:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 8:25 [PATCH] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-11 18:07 ` Darrick J. Wong
2018-01-12 1:58 ` Xiao Yang
2018-01-12 6:14 ` [PATCH v2] syscalls/madvise09.c: Use custom mount point instead of /sys/fs/cgroup/memory xiao yang
2018-01-12 6:14 ` [PATCH v2] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-12 6:19 ` Xiao Yang [this message]
2018-01-12 6:16 ` [PATCH v2 1/2] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-12 6:16 ` [PATCH v2 2/2] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-12 7:49 ` Eryu Guan
2018-01-12 8:36 ` Dave Chinner
2018-01-12 8:50 ` Eryu Guan
2018-01-12 16:41 ` Darrick J. Wong
2018-01-13 2:23 ` Dave Chinner
2018-01-15 6:29 ` Eryu Guan
2018-01-15 7:48 ` [PATCH v3 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-15 7:48 ` [PATCH v3 2/3] common/filter: factor out expected XFS warnings for mount xiao yang
2018-01-15 7:48 ` [PATCH v3 3/3] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-15 12:45 ` [PATCH v2 2/2] " Brian Foster
2018-01-15 21:03 ` Dave Chinner
2018-01-16 4:02 ` Eryu Guan
2018-01-16 6:41 ` Xiao Yang
2018-01-16 7:26 ` [PATCH v4 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-16 7:26 ` [PATCH v4 2/3] common/filter: factor out expected XFS warnings for mount xiao yang
2018-01-18 8:48 ` Eryu Guan
2018-01-18 8:56 ` Xiao Yang
2018-01-16 7:26 ` [PATCH v4 3/3] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-18 8:46 ` Eryu Guan
2018-01-18 10:49 ` [PATCH v5 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-18 10:49 ` [PATCH v5 2/3] common/filter: Factor out expected XFS warnings for assert xiao yang
2018-01-18 18:29 ` Darrick J. Wong
2018-01-19 2:51 ` Eryu Guan
2018-01-19 4:04 ` Xiao Yang
2018-01-19 5:38 ` [PATCH v6 2/3] common: Add _require_no_xfs_bug_on_assert && Factor out filter_xfs_dmesg xiao yang
2018-01-19 5:38 ` [PATCH v6 3/3] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-18 10:49 ` [PATCH v5 " xiao yang
2018-01-18 18:19 ` [PATCH v5 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db Darrick J. Wong
2018-01-16 8:50 ` [PATCH v2 2/2] xfs: Regression test for invalid sb_logsunit Dave Chinner
2018-01-16 14:09 ` Brian Foster
2018-01-18 8:44 ` Eryu Guan
2018-01-16 13:58 ` Brian Foster
2018-01-12 7:44 ` [PATCH v2 1/2] common/xfs: Check if write supports [-c|-d] option in xfs_db Eryu Guan
2018-01-12 16:43 ` Darrick J. Wong
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=5A585378.70900@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--cc=darrick.wong@oracle.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
/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