From: Rich Johnston <rjohnston@sgi.com>
To: Dwight Engen <dwight.engen@oracle.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] xfstests: add nsexec user namespace helper
Date: Mon, 19 Aug 2013 10:03:29 -0500 [thread overview]
Message-ID: <521233C1.1050908@sgi.com> (raw)
In-Reply-To: <20130627120328.2ed716ef@oracle.com>
Thanks for the patch Dwight, it has been committed.
--Rich
commit 3f424be6396205edd6aec1d46de04349aebe9306
Author: Dwight Engen <dwight.engen@oracle.com>
Date: Thu Jun 27 16:03:28 2013 +0000
xfstests: add nsexec user namespace helper
Add new program nsexec to facilitate creating/entering a user
namespace. The
original source for the program is https://lwn.net/Articles/539940.
I added
the -s option to become "root" in the user namespace.
Signed-off-by: Dwight Engen <dwight.engen@oracle.com>
Reviewed-by: <rjohnston@sgi.com>
Signed-off-by: <rjohnston@sgi.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-08-19 15:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 19:34 [PATCH] xfstests: 313,314: user namespace uid/gids in inode, ACL Dwight Engen
2013-06-26 1:09 ` Dave Chinner
2013-06-26 16:30 ` Dwight Engen
2013-06-27 16:03 ` [PATCH 1/3] xfstests: add nsexec user namespace helper Dwight Engen
2013-08-19 14:10 ` Rich Johnston
2013-08-19 15:03 ` Rich Johnston [this message]
2013-06-27 16:03 ` [PATCH 2/3] xfstests 313: user namespace uid/gids in an inode Dwight Engen
2013-08-19 14:10 ` Rich Johnston
2013-08-19 15:03 ` Rich Johnston
2013-06-27 16:03 ` [PATCH 3/3] xfstests 314: user namespace uid/gids in an ACL Dwight Engen
2013-08-19 14:11 ` Rich Johnston
2013-08-19 17:34 ` Dwight Engen
2013-08-19 17:34 ` [PATCH v2] xfstests generic/318: " Dwight Engen
2013-08-19 20:49 ` Rich Johnston
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=521233C1.1050908@sgi.com \
--to=rjohnston@sgi.com \
--cc=dwight.engen@oracle.com \
--cc=xfs@oss.sgi.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.