From: Miklos Szeredi <miklos@szeredi.hu>
To: Amir Goldstein <amir73il@gmail.com>
Cc: "linux-unionfs@vger.kernel.org" <linux-unionfs@vger.kernel.org>
Subject: Re: [PATCH] ovl: fix nested overlayfs mount
Date: Wed, 16 Nov 2016 10:28:17 +0100 [thread overview]
Message-ID: <CAJfpegsBgNa0AYibyDwq-B5R5a7R6y6zMvmwzzBJXDNee-tv_A@mail.gmail.com> (raw)
In-Reply-To: <1479288159-20396-1-git-send-email-amir73il@gmail.com>
On Wed, Nov 16, 2016 at 10:22 AM, Amir Goldstein <amir73il@gmail.com> wrote:
> The introduction of overlayfs features broke nested mounting
> of overlayfs as lowerdir of another overlayfs mount.
>
> When the upper overlayfs checks overlayfs features xattr
> on the underlying overlayfs mount, it gets -EPERM and aborts.
>
> Fix this by returning -ENODATA instead of -EPERM from
> ovl_own_xattr_get(). This behavior is consistent with the
> behavior of ovl_listxattr(), which filters out the private
> overlayfs xattrs.
Yes, it makes sense regardless of the features xattr.
Applied.
Thanks,
Miklos
prev parent reply other threads:[~2016-11-16 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 9:22 [PATCH] ovl: fix nested overlayfs mount Amir Goldstein
2016-11-16 9:28 ` 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=CAJfpegsBgNa0AYibyDwq-B5R5a7R6y6zMvmwzzBJXDNee-tv_A@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=amir73il@gmail.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).