From: Vivek Goyal <vgoyal@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: "Miklos Szeredi" <miklos@szeredi.hu>,
"Theodore Y . Ts'o" <tytso@mit.edu>,
"Maciej Zięba" <maciekz82@gmail.com>,
linux-unionfs@vger.kernel.org
Subject: Re: [PATCH] ovl: fix missing override creds in link of a metacopy upper
Date: Wed, 14 Nov 2018 09:17:32 -0500 [thread overview]
Message-ID: <20181114141732.GA29804@redhat.com> (raw)
In-Reply-To: <20181114140134.6996-1-amir73il@gmail.com>
On Wed, Nov 14, 2018 at 04:01:34PM +0200, Amir Goldstein wrote:
> Theodore Ts'o reported a v4.19 regression with docker-dropbox:
> https://marc.info/?l=linux-fsdevel&m=154070089431116&w=2
>
> "I was rebuilding my dropbox Docker container, and it failed in 4.19
> with the following error:
> ...
> dpkg: error: error creating new backup file \
> '/var/lib/dpkg/status-old': Invalid cross-device link"
>
> The problem did not reproduce with metacopy feature disabled.
> The error was caused by insufficient credentials to set
> "trusted.overlay.redirect" xattr on link of a metacopy file.
>
Thanks Amir for fixiing this. This fix looks good to me.
Acked-by: Vivek Goyal <vgoyal@redhat.com>
So this problem happened because looks like kernel enanbled metacopy
by default (in Kconfig) and thence enabled redirect by default in Kconfig.
I am wondering how does that impact docker build process. Because if
redirect/metacopy is enabled, while during diff, docker falls back to
using older naivediff interface as opposed to newer nativediff. I am
not sure how slower naivediff is as compared to nativediff. I am raising
this point here because I am curious. If somebody has that info, please
share.
Thanks
Vivek
> Reproducer:
>
> echo Y > /sys/module/overlay/parameters/redirect_dir
> echo Y > /sys/module/overlay/parameters/metacopy
> cd /tmp
> mkdir l u w m
> chmod 777 l u
> touch l/foo
> ln l/foo l/link
> chmod 666 l/foo
> mount -t overlay none -olowerdir=l,upperdir=u,workdir=w m
> su fsgqa
> ln m/foo m/bar
> [ 21.455823] overlayfs: failed to set redirect (-1)
> ln: failed to create hard link 'm/bar' => 'm/foo':\
> Invalid cross-device link
>
> Reported-by: Theodore Y. Ts'o <tytso@mit.edu>
> Reported-by: Maciej Zięba <maciekz82@gmail.com>
> Fixes: 4120fe64dce4 ("ovl: Set redirect on upper inode when it is linked")
> Cc: <stable@vger.kernel.org> # v4.19
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> ---
> fs/overlayfs/dir.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/fs/overlayfs/dir.c b/fs/overlayfs/dir.c
> index c6289147c787..82c129bfe58d 100644
> --- a/fs/overlayfs/dir.c
> +++ b/fs/overlayfs/dir.c
> @@ -651,6 +651,18 @@ static int ovl_symlink(struct inode *dir, struct dentry *dentry,
> return ovl_create_object(dentry, S_IFLNK, 0, link);
> }
>
> +static int ovl_set_link_redirect(struct dentry *dentry)
> +{
> + const struct cred *old_cred;
> + int err;
> +
> + old_cred = ovl_override_creds(dentry->d_sb);
> + err = ovl_set_redirect(dentry, false);
> + revert_creds(old_cred);
> +
> + return err;
> +}
> +
> static int ovl_link(struct dentry *old, struct inode *newdir,
> struct dentry *new)
> {
> @@ -670,7 +682,7 @@ static int ovl_link(struct dentry *old, struct inode *newdir,
> goto out_drop_write;
>
> if (ovl_is_metacopy_dentry(old)) {
> - err = ovl_set_redirect(old, false);
> + err = ovl_set_link_redirect(old);
> if (err)
> goto out_drop_write;
> }
> --
> 2.17.1
>
next prev parent reply other threads:[~2018-11-14 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 14:01 [PATCH] ovl: fix missing override creds in link of a metacopy upper Amir Goldstein
2018-11-14 14:17 ` Vivek Goyal [this message]
2018-11-14 14:48 ` Miklos Szeredi
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=20181114141732.GA29804@redhat.com \
--to=vgoyal@redhat.com \
--cc=amir73il@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=maciekz82@gmail.com \
--cc=miklos@szeredi.hu \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.