All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: Yuan Sun <sunyuan3@huawei.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] userns02: add SAFE_CLOSE
Date: Tue, 16 Jun 2015 10:03:25 -0400 (EDT)	[thread overview]
Message-ID: <105649905.2697646.1434463405501.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1434491631-28506-1-git-send-email-sunyuan3@huawei.com>





----- Original Message -----
> From: "Yuan Sun" <sunyuan3@huawei.com>
> To: jstancek@redhat.com
> Cc: ltp-list@lists.sourceforge.net
> Sent: Tuesday, 16 June, 2015 11:53:51 PM
> Subject: [PATCH] userns02: add SAFE_CLOSE
> 
> Signed-off-by: Yuan Sun <sunyuan3@huawei.com>
> ---
>  testcases/kernel/containers/userns/userns02.c | 24 +++++++++++++-----------
>  1 file changed, 13 insertions(+), 11 deletions(-)
> 
> diff --git a/testcases/kernel/containers/userns/userns02.c
> b/testcases/kernel/containers/userns/userns02.c
> index ad5dda5..f5feceb 100644
> --- a/testcases/kernel/containers/userns/userns02.c
> +++ b/testcases/kernel/containers/userns/userns02.c
> @@ -31,6 +31,11 @@
>  char *TCID = "user_namespace2";
>  int TST_TOTAL = 1;
>  
> +static void cleanup(void)
> +{
> +	tst_rmdir();
> +}
> +
>  /*
>   * child_fn1() - Inside a new user namespace
>   */
> @@ -39,7 +44,7 @@ static int child_fn1(void)
>  	int exit_val;
>  	int uid, gid;
>  
> -	TST_SAFE_CHECKPOINT_WAIT(NULL, 0);
> +	TST_SAFE_CHECKPOINT_WAIT(cleanup, 0);

You shouldn't call cleanup from child. The rest looks OK.

Regards,
Jan

>  	uid = geteuid();
>  	gid = getegid();
>  
> @@ -62,11 +67,6 @@ static void setup(void)
>  	TST_CHECKPOINT_INIT(NULL);
>  }
>  
> -static void cleanup(void)
> -{
> -	tst_rmdir();
> -}
> -
>  int main(int argc, char *argv[])
>  {
>  	int status;
> @@ -93,14 +93,16 @@ int main(int argc, char *argv[])
>  		parentgid = getegid();
>  		sprintf(path, "/proc/%d/uid_map", childpid);
>  		sprintf(content, "100 %d 1", parentuid);
> -		fd = SAFE_OPEN(NULL, path, O_WRONLY, 0644);
> -		SAFE_WRITE(NULL, 1, fd, content, strlen(content));
> +		fd = SAFE_OPEN(cleanup, path, O_WRONLY, 0644);
> +		SAFE_WRITE(cleanup, 1, fd, content, strlen(content));
> +		SAFE_CLOSE(cleanup, fd);
>  		sprintf(path, "/proc/%d/gid_map", childpid);
>  		sprintf(content, "100 %d 1", parentgid);
> -		fd = SAFE_OPEN(NULL, path, O_WRONLY, 0644);
> -		SAFE_WRITE(NULL, 1, fd, content, strlen(content));
> +		fd = SAFE_OPEN(cleanup, path, O_WRONLY, 0644);
> +		SAFE_WRITE(cleanup, 1, fd, content, strlen(content));
> +		SAFE_CLOSE(cleanup, fd);
>  
> -		TST_SAFE_CHECKPOINT_WAKE(NULL, 0);
> +		TST_SAFE_CHECKPOINT_WAKE(cleanup, 0);
>  
>  		if (waitpid(childpid, &status, 0) < 0)
>  			tst_brkm(TBROK | TERRNO, cleanup, "waitpid failed");
> --
> 1.9.1
> 
> 

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      reply	other threads:[~2015-06-16 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 21:53 [LTP] [PATCH] userns02: add SAFE_CLOSE Yuan Sun
2015-06-16 14:03 ` Jan Stancek [this message]

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=105649905.2697646.1434463405501.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=sunyuan3@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.