From: Dave Chinner <david@fromorbit.com>
To: Dwight Engen <dwight.engen@oracle.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: 313,314: user namespace uid/gids in inode, ACL
Date: Wed, 26 Jun 2013 11:09:31 +1000 [thread overview]
Message-ID: <20130626010931.GA29376@dastard> (raw)
In-Reply-To: <20130625153443.08142635@oracle.com>
On Tue, Jun 25, 2013 at 03:34:43PM -0400, Dwight Engen wrote:
> These tests verify that the uid/gids in an inode and in ACLs get translated
> from/to a user namespace to/from disk correctly.
>
> I had to use getfacl instead of the chacl -l because I need numeric uids
> to make the output consistent.
>
> A new program nsexec was added to facilitate creating/entering a user
> namespace for testing. The orignal source for the program is
> https://lwn.net/Articles/539940. I added the -s option to become "root"
> in the user namespace.
>
> Tested against btrfs, ext4, and xfs with my proposed user namespace changes.
Can you split it out into a patch per test? It's easier to review
that way...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-06-26 1:10 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 [this message]
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
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=20130626010931.GA29376@dastard \
--to=david@fromorbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox