All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Josh England <jjengla@gmail.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-unionfs@vger.kernel.org,
	Miklos Szeredi <mszeredi@redhat.com>
Subject: Re: overlayfs: allowing for changes to lowerdir
Date: Tue, 28 Feb 2017 19:44:57 +0000	[thread overview]
Message-ID: <20170228194457.GU29622@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+ZH+jE0k2hKoWTMZ2g-5vfU95OFxbW=WxGEC-umQM51vcC1gQ@mail.gmail.com>

On Tue, Feb 28, 2017 at 11:08:31AM -0800, Josh England wrote:

> The behavior I've noted so far from this patch seems to be very well
> defined and follows the rule of least surprise (at least for me).  I
> can change files/directories in the shared root and the changes are
> instantly visible to all clients.  If a file/directory has been copied
> up on the client that change takes precedence over changes in the
> lower.  Deletes work as expected.  I haven't found a downside yet.

Try to do something that invalidates a directory in underlying layer
with stuff in overlay on its subdirectories. 

  reply	other threads:[~2017-02-28 19:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 21:41 overlayfs: allowing for changes to lowerdir Josh England
2017-02-14 14:01 ` Amir Goldstein
2017-02-14 17:14   ` Josh England
2017-02-21 23:08   ` Josh England
2017-02-22  9:00     ` Ian Kent
2017-02-27 10:40     ` Amir Goldstein
2017-02-28 19:08       ` Josh England
2017-02-28 19:44         ` Al Viro [this message]
2017-03-01 11:15           ` Amir Goldstein
2017-03-01 18:22           ` Josh England
2017-03-01 20:22         ` Colin Walters
2017-03-09 10:37   ` Miklos Szeredi
2017-03-09 11:22     ` Amir Goldstein
2017-03-09 13:12       ` Miklos Szeredi
2017-02-15  1:29 ` J. R. Okajima

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=20170228194457.GU29622@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=amir73il@gmail.com \
    --cc=jjengla@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=mszeredi@redhat.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.