All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	Chandan Rajendra <chandan@linux.vnet.ibm.com>,
	zhangyi <yi.zhang@huawei.com>,
	overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: [PATCH v5 2/4] ovl: allocate anonymous devs for lowerdirs
Date: Thu, 2 Nov 2017 08:27:30 -0400	[thread overview]
Message-ID: <20171102122730.GA16677@redhat.com> (raw)
In-Reply-To: <CAOQ4uxhpq_mEyyUj0M5AELPYGuHwyCpxz9+HE4K0qaY1+-XQGw@mail.gmail.com>

On Wed, Nov 01, 2017 at 06:41:51PM +0200, Amir Goldstein wrote:

[..]
> >> I can't remember if there was a reason for not allocating anonymous bdev
> >> for upper
> >
> > That's a good point.
> >
> >> or if it just because we did not need it to guaranty uniqueness
> >> of st_dev/st_ino *among* overlay inodes
> >
> > Even for lower, st_dev will be unique for different lower on non same-fs,
> > right. IOW, when it come to uniqueness of st_dev/st_ino pair, among
> > overlay inodes, lower and upper should have same requirements.
> >
> >> while guarantying constant
> >> st_dev/st_ino across copy up.
> >
> > Hmm..., I did not get this point. Over copy up, atleast st_ino will change
> > for non-samefs case.
> >
> > I will spend more time on patch.
> >
> 
> Urgh! It took me a while to remember the reason why system wide uniqueness
> is important for lower but less for upper.
> An upper object has the same content as the "real" object and they have the
> same st_ino/st_dev so its ok that diff will skip comparing them.
> A copy-up object does not have the same content as the lower "real" object,
> so if it has the same st_ino/st_dev as real object, diff will skip compare and
> we have a problem.

I am not sure I understand this.  So you are doing a diff between a file
on overlayfs and same file accessed outside overlayfs?

If a file is on lower, then it has not been modified and diff skipping
it makes perfect sense?

Vivek

  reply	other threads:[~2017-11-02 12:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 20:27 [PATCH v5 0/4] Overlayfs: constant st_ino/d_ino for non-samefs Amir Goldstein
2017-10-30 20:27 ` [PATCH v5 1/4] ovl: move include of ovl_entry.h into overlayfs.h Amir Goldstein
2017-10-31 13:14   ` Miklos Szeredi
2017-10-31 13:22     ` Amir Goldstein
2017-10-30 20:27 ` [PATCH v5 2/4] ovl: allocate anonymous devs for lowerdirs Amir Goldstein
2017-10-31 13:43   ` Miklos Szeredi
2017-10-31 13:53     ` Amir Goldstein
2017-10-31 23:01       ` Amir Goldstein
2017-11-01 13:17         ` Chandan Rajendra
2017-11-01 13:34           ` Amir Goldstein
2017-11-01 14:42   ` Vivek Goyal
2017-11-01 15:02     ` Amir Goldstein
2017-11-01 15:47       ` Vivek Goyal
2017-11-01 16:41         ` Amir Goldstein
2017-11-02 12:27           ` Vivek Goyal [this message]
2017-11-02 12:47             ` Amir Goldstein
2017-11-02 14:05               ` Vivek Goyal
2017-11-02 14:38                 ` Amir Goldstein
2017-11-01 15:41   ` Vivek Goyal
2017-11-01 16:30     ` Amir Goldstein
2017-10-30 20:27 ` [PATCH v5 3/4] ovl: relax same fs constrain for constant st_ino Amir Goldstein
2017-10-30 20:27 ` [PATCH v5 4/4] ovl: relax same fs constraint for constant d_ino Amir Goldstein

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=20171102122730.GA16677@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=amir73il@gmail.com \
    --cc=chandan@linux.vnet.ibm.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=yi.zhang@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.