public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] syscalls/madvise09.c: Use custom mount point instead of /sys/fs/cgroup/memory
Date: Mon, 15 Jan 2018 03:06:02 -0500 (EST)	[thread overview]
Message-ID: <1801982516.6465238.1516003561998.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <5A5C3E27.1050702@cn.fujitsu.com>



----- Original Message -----
> Hi Jan,
> 
> Could you help me review this patch.

Hi,

I think it would be better to use existing mount, if it's already mounted.
umount may fail with -EBUSY if the subsystem is already part of existing
hierarchy.

Regards,
Jan

> 
> Thanks,
> Xiao Yang
> On 2018/01/04 10:43, 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;
> 
> 
> 
> 

  reply	other threads:[~2018-01-15  8:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-27  7:40 [LTP] [PATCH] syscalls/madvise09.c: Use custom mount point instead of /sys/fs/cgroup/memory xiao yang
2018-01-04  2:43 ` Xiao Yang
2018-01-04  2:43   ` [LTP] [PATCH v2] " xiao yang
2018-01-15  5:37     ` Xiao Yang
2018-01-15  8:06       ` Jan Stancek [this message]
2018-01-15  9:27         ` Xiao Yang
2018-01-15 15:58           ` Jan Stancek
2018-01-16  9:11             ` Xiao Yang
2018-01-16  9:19               ` Xiao Yang
2018-01-16 10:32                 ` 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=1801982516.6465238.1516003561998.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox