From: Vivek Goyal <vgoyal@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
yangerkun <yangerkun@huawei.com>,
overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: [PATCH 2/3] overlayfs: ovl_lookup(): Use only uppermetacopy state
Date: Mon, 1 Jun 2020 11:22:52 -0400 [thread overview]
Message-ID: <20200601152252.GB3219@redhat.com> (raw)
In-Reply-To: <CAOQ4uxi08jyGa_aPBLxWoF1649+6CzZ6iJtiz76cKUvWRnpVvA@mail.gmail.com>
On Sat, May 30, 2020 at 02:01:28PM +0300, Amir Goldstein wrote:
[..]
> > @@ -982,23 +987,17 @@ struct dentry *ovl_lookup(struct inode *dir, struct dentry *dentry,
> > }
> > }
> >
> > - if (metacopy) {
> > - /*
> > - * Found a metacopy dentry but did not find corresponding
> > - * data dentry
> > - */
> > - if (d.metacopy) {
> > - err = -EIO;
> > - goto out_put;
> > - }
> > + /* Found a metacopy dentry but did not find corresponding data dentry */
> > + if (d.metacopy) {
>
> I suggested this change and I think it is correct, but it is correct for a bit
> of a subtle reason.
> It is correct because ovl_lookup_layer() (currently) cannot return NULL
> and set d.metacopy to false.
> So I suggest to be a bit more defensive and write this condition as:
>
> if (d.metacopy || (uppermetacopy && !ctr)) {
Ok, will do.
>
> > + err = -EIO;
> > + goto out_put;
> > + }
> >
> > - err = -EPERM;
> > - if (!ofs->config.metacopy) {
> > - pr_warn_ratelimited("refusing to follow metacopy origin for (%pd2)\n",
> > - dentry);
> > - goto out_put;
> > - }
> > - } else if (!d.is_dir && upperdentry && !ctr && origin_path) {
> > + /* For regular non-metacopy upper dentries, there is no lower
> > + * path based lookup, hence ctr will be zero. dentry found using
> > + * ORIGIN xattr on upper, install it in stack.
> > + */
> > + if (!d.is_dir && upperdentry && !ctr && origin_path) {
>
> I don't like this comment style for multi line comment and I don't
> like that you detached this if statement from else if.
> I think it made more sense with the else because this is (as you write)
> the non-metacopy case.
Will do in V2.
Thanks
Vivek
next prev parent reply other threads:[~2020-06-01 15:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 21:29 [PATCH 0/3] overlayfs: Do not check metacopy in ovl_get_inode() Vivek Goyal
2020-05-29 21:29 ` [PATCH 1/3] overlayfs: Simplify setting of origin for index lookup Vivek Goyal
2020-05-30 10:37 ` Amir Goldstein
2020-06-01 14:04 ` Vivek Goyal
2020-06-01 15:15 ` Amir Goldstein
2020-06-01 17:51 ` Vivek Goyal
2020-05-29 21:29 ` [PATCH 2/3] overlayfs: ovl_lookup(): Use only uppermetacopy state Vivek Goyal
2020-05-30 11:01 ` Amir Goldstein
2020-06-01 15:22 ` Vivek Goyal [this message]
2020-05-29 21:29 ` [PATCH 3/3] overlayfs: Initialize OVL_UPPERDATA in ovl_lookup() Vivek Goyal
2020-05-30 11:02 ` Amir Goldstein
2020-05-30 0:59 ` [PATCH 0/3] overlayfs: Do not check metacopy in ovl_get_inode() yangerkun
2020-05-30 3:55 ` yangerkun
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=20200601152252.GB3219@redhat.com \
--to=vgoyal@redhat.com \
--cc=amir73il@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=yangerkun@huawei.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 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.