From: Miklos Szeredi <miklos@szeredi.hu>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: "linux-unionfs@vger.kernel.org" <linux-unionfs@vger.kernel.org>
Subject: Re: [PATCH] ovl: Fix for filesystems without POSIX ACL support
Date: Tue, 6 Sep 2016 14:47:01 +0200 [thread overview]
Message-ID: <CAJfpegt5JJM7zvb=AOmuhs1fEMz002Gb8=sGH1pONs6phpdDKw@mail.gmail.com> (raw)
In-Reply-To: <1473164020-13364-1-git-send-email-agruenba@redhat.com>
On Tue, Sep 6, 2016 at 2:13 PM, Andreas Gruenbacher <agruenba@redhat.com> wrote:
> On filesystems without POSIX ACL support such as ubifs, trying to remove
> a POSIX ACL with vfs_removexattr will result in -EOPNOTSUPP. Don't fail
> in that case.
>
Yep, already fixed in overlayfs-linus.
Thanks,
Miklos
> Reported-by: Richard Weinberger <richard@nod.at>
> Fixes: c11b9fdd
> Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
> ---
> fs/overlayfs/super.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
> index a4585f9..e2a94a2 100644
> --- a/fs/overlayfs/super.c
> +++ b/fs/overlayfs/super.c
> @@ -835,11 +835,11 @@ retry:
> goto out_dput;
>
> err = vfs_removexattr(work, XATTR_NAME_POSIX_ACL_DEFAULT);
> - if (err && err != -ENODATA)
> + if (err && err != -ENODATA && err != -EOPNOTSUPP)
> goto out_dput;
>
> err = vfs_removexattr(work, XATTR_NAME_POSIX_ACL_ACCESS);
> - if (err && err != -ENODATA)
> + if (err && err != -ENODATA && err != -EOPNOTSUPP)
> goto out_dput;
>
> /* Clear any inherited mode bits */
> --
> 2.7.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-09-06 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 12:13 [PATCH] ovl: Fix for filesystems without POSIX ACL support Andreas Gruenbacher
2016-09-06 12:47 ` Miklos Szeredi [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='CAJfpegt5JJM7zvb=AOmuhs1fEMz002Gb8=sGH1pONs6phpdDKw@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=agruenba@redhat.com \
--cc=linux-unionfs@vger.kernel.org \
/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).