From: Vivek Goyal <vgoyal@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Andreas Gruenbacher <agruenba@redhat.com>,
linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] ovl: update S_ISGID when setting posix ACLs
Date: Thu, 27 Oct 2016 18:37:42 -0400 [thread overview]
Message-ID: <20161027223742.GC4819@redhat.com> (raw)
In-Reply-To: <1477506616-14061-1-git-send-email-amir73il@gmail.com>
On Wed, Oct 26, 2016 at 09:30:16PM +0300, Amir Goldstein wrote:
> Since operations on upper are performed using mounter's credentials,
> we need to call posix_acl_update_mode() with current credentials on
> overlay inode to possibly copy-up and clear setgid bit, before setting
> posix ACLs on upper inode.
>
> Also wrap posix acl handlers with #ifdef CONFIG_FS_POSIX_ACL to
> avoid compiler warning for implicit declaration of function
> 'posix_acl_update_mode' on build without that config option.
>
> This change fixes xfstest generic/375, which failed to clear the
> setgid bit in the following test case over overlayfs:
>
> touch $testfile
> chown 100:100 $testfile
> chmod 2755 $testfile
> _runas -u 100 -g 101 -- setfacl -m u::rwx,g::rwx,o::rwx $testfile
>
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> ---
> fs/overlayfs/super.c | 31 +++++++++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
> index 30263a5..7071790 100644
> --- a/fs/overlayfs/super.c
> +++ b/fs/overlayfs/super.c
> @@ -523,6 +523,22 @@ static unsigned int ovl_split_lowerdirs(char *str)
> }
>
> static int __maybe_unused
> +ovl_set_mode(struct dentry *dentry, umode_t mode)
> +{
> + struct iattr iattr;
> +
> + if (mode == d_inode(dentry)->i_mode)
> + return 0;
> +
> + iattr.ia_valid = ATTR_MODE | ATTR_CTIME;
> + iattr.ia_mode = mode;
> + iattr.ia_ctime = current_time(d_inode(dentry));
> +
> + return ovl_setattr(dentry, &iattr);
> +}
> +
> +#ifdef CONFIG_FS_POSIX_ACL
> +static int __maybe_unused
> ovl_posix_acl_xattr_get(const struct xattr_handler *handler,
> struct dentry *dentry, struct inode *inode,
> const char *name, void *buffer, size_t size)
> @@ -560,6 +576,18 @@ ovl_posix_acl_xattr_set(const struct xattr_handler *handler,
> if (!inode_owner_or_capable(inode))
> goto out_acl_release;
>
> + if (handler->flags == ACL_TYPE_ACCESS) {
> + umode_t mode;
> + struct posix_acl *newacl = acl;
> +
> + err = posix_acl_update_mode(inode, &mode, &newacl);
> + if (err)
> + goto out_acl_release;
> + err = ovl_set_mode(dentry, mode);
> + if (err)
> + goto out_acl_release;
> + }
> +
> posix_acl_release(acl);
>
> err = ovl_xattr_set(dentry, handler->name, value, size, flags);
> @@ -572,6 +600,7 @@ ovl_posix_acl_xattr_set(const struct xattr_handler *handler,
Hi Amir,
What happens if ovl_set_mode() is successful but ovl_xattr_set() fails. We
will leave file with S_ISGID clear?
Vivek
> posix_acl_release(acl);
> return err;
> }
> +#endif
>
> static int ovl_own_xattr_get(const struct xattr_handler *handler,
> struct dentry *dentry, struct inode *inode,
> @@ -603,6 +632,7 @@ static int ovl_other_xattr_set(const struct xattr_handler *handler,
> return ovl_xattr_set(dentry, name, value, size, flags);
> }
>
> +#ifdef CONFIG_FS_POSIX_ACL
> static const struct xattr_handler __maybe_unused
> ovl_posix_acl_access_xattr_handler = {
> .name = XATTR_NAME_POSIX_ACL_ACCESS,
> @@ -618,6 +648,7 @@ ovl_posix_acl_default_xattr_handler = {
> .get = ovl_posix_acl_xattr_get,
> .set = ovl_posix_acl_xattr_set,
> };
> +#endif
>
> static const struct xattr_handler ovl_own_xattr_handler = {
> .prefix = OVL_XATTR_PREFIX,
> --
> 2.7.4
next prev parent reply other threads:[~2016-10-27 22:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 17:10 [PATCH] ovl: update S_ISGID when setting posix ACLs Amir Goldstein
2016-10-26 18:30 ` [PATCH v2] " Amir Goldstein
2016-10-26 18:52 ` Andreas Gruenbacher
2016-10-27 22:37 ` Vivek Goyal [this message]
2016-10-28 4:47 ` Amir Goldstein
2016-10-28 12:54 ` Miklos Szeredi
2016-10-28 19:22 ` Amir Goldstein
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=20161027223742.GC4819@redhat.com \
--to=vgoyal@redhat.com \
--cc=agruenba@redhat.com \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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;
as well as URLs for NNTP newsgroup(s).