All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: overlayfs <linux-unionfs@vger.kernel.org>,
	Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [PATCH 8/8] ovl: Fix ovl_getattr() to get number of blocks from lower
Date: Mon, 9 Oct 2017 10:45:23 -0400	[thread overview]
Message-ID: <20171009144523.GD29869@redhat.com> (raw)
In-Reply-To: <CAOQ4uxh4fcDc4FovOW_9vNGVJ3mDKrT=YVyXBNOFQAL_a2Gh_w@mail.gmail.com>

On Fri, Oct 06, 2017 at 10:09:38PM +0300, Amir Goldstein wrote:

[..]
> >> > @@ -140,6 +143,17 @@ int ovl_getattr(const struct path *path, struct kstat *stat,
> >> >         if (!is_dir && ovl_test_flag(OVL_INDEX, d_inode(dentry)))
> >> >                 stat->nlink = dentry->d_inode->i_nlink;
> >> >
> >> > +       if (ovl_test_flag(OVL_METACOPY, d_inode(dentry))) {
> >> > +               u32 lowermask = STATX_BLOCKS;
> >> > +
> >> > +               if (!lowerstat_done) {
> >>
> >> I guess lowerstat_done is as result from my comment,
> >> but I did not mean I think vfs_getattr() is expensive,
> >> I just didn't like the duplication of that code block, but maybe
> >> just a matter of personal taste.
> >> Can be sorted out later.
> >
> > Yes, I added this because I thought you wanted to avoid that extra
> > vfs_getattr() call. I am open to change it whatever way you like.
> > Personally I did not like this extra boolean and I liked unconditional
> > vfs_getattr() better. It was not most optimized but was easier to
> > understand.
> >
> 
> Yeh, I liked it without the boolean better as well.
> What I meant is once this patch lands:
> https://github.com/chandanr/linux/commit/e9024b0a08a1c725daed548f68ff703305c40124
> vfs_getattr() will be called for all non-dir with ORIGIN anyway, so
> METACOPY will be able to piggy back STATX_BLOCKS flag on the same call.

Aha, got it. Once these patches are merged, I will rebase my patch on top
of it. 

In the mean time, for the purpose of review and test, I will continue with my
patch.

Vivek

      reply	other threads:[~2017-10-09 14:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06 17:47 [RFC PATCH 0/8][V2] overlayfs: Delayed copy up of data Vivek Goyal
2017-10-06 17:47 ` [PATCH 1/8] ovl: ovl_check_setxattr() get rid of redundant -EOPNOTSUPP check Vivek Goyal
2017-10-06 17:47 ` [PATCH 2/8] ovl: During copy up, first copy up metadata and then data Vivek Goyal
2017-10-06 17:47 ` [PATCH 3/8] ovl: Provide a mount option metacopy=on/off for metadata copyup Vivek Goyal
2017-10-06 19:01   ` Amir Goldstein
2017-10-09 14:53     ` Vivek Goyal
2017-10-06 17:47 ` [PATCH 4/8] ovl: Copy up only metadata during copy up where it makes sense Vivek Goyal
2017-10-06 17:47 ` [PATCH 5/8] ovl: Set xattr OVL_XATTR_METACOPY on upper file Vivek Goyal
2017-10-06 17:47 ` [PATCH 6/8] ovl: Set OVL_METACOPY flag during ovl_lookup() Vivek Goyal
2017-10-06 17:47 ` [PATCH 7/8] ovl: Return lower dentry if only metadata copy up took place Vivek Goyal
2017-10-06 17:47 ` [PATCH 8/8] ovl: Fix ovl_getattr() to get number of blocks from lower Vivek Goyal
2017-10-06 18:58   ` Amir Goldstein
2017-10-06 19:01     ` Vivek Goyal
2017-10-06 19:09       ` Amir Goldstein
2017-10-09 14:45         ` Vivek Goyal [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=20171009144523.GD29869@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=amir73il@gmail.com \
    --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 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.