From: Gao feng <gaofeng@cn.fujitsu.com>
To: Dwight Engen <dwight.engen@oracle.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH v7 2/7] xfs: convert kuid_t to/from uid_t in ACLs
Date: Wed, 31 Jul 2013 14:51:25 +0800 [thread overview]
Message-ID: <51F8B3ED.7040808@cn.fujitsu.com> (raw)
In-Reply-To: <20130729230646.715303ed@oracle.com>
On 07/30/2013 11:06 AM, Dwight Engen wrote:
> Change permission check for setting ACL to use inode_owner_or_capable()
> which will additionally allow a CAP_FOWNER user in a user namespace to
> be able to set an ACL on an inode covered by the user namespace mapping.
>
> Reviewed-by: Dave Chinner <dchinner@redhat.com>
> Signed-off-by: Dwight Engen <dwight.engen@oracle.com>
> ---
> fs/xfs/xfs_acl.c | 20 ++++++++++++++++----
> 1 file changed, 16 insertions(+), 4 deletions(-)
Reviewed-by: Gao feng <gaofeng@cn.fujitsu.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-07-31 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 3:06 [PATCH v7 2/7] xfs: convert kuid_t to/from uid_t in ACLs Dwight Engen
2013-07-31 6:51 ` Gao feng [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=51F8B3ED.7040808@cn.fujitsu.com \
--to=gaofeng@cn.fujitsu.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