linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Kevin Locke <kevin@kevinlocke.name>
Cc: overlayfs <linux-unionfs@vger.kernel.org>,
	Amir Goldstein <amir73il@gmail.com>,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH v2] ovl: document lower modification caveats
Date: Fri, 30 Oct 2020 14:16:46 +0100	[thread overview]
Message-ID: <CAJfpegvakND7=_8eDdu9TAgXwYNN-vZi1pdY-gLzuF-Dn6C0_Q@mail.gmail.com> (raw)
In-Reply-To: <fe78446e6565cda29cc2c87f3e3c1b2a16f5d5cc.1598149357.git.kevin@kevinlocke.name>

On Sun, Aug 23, 2020 at 4:23 AM Kevin Locke <kevin@kevinlocke.name> wrote:
>
> Some overlayfs optional features are incompatible with offline changes
> to the lower tree[1][2][3] and may result in -EXDEV[4], -EIO[5], or
> other errors.  Such modification is not supported and the error behavior
> is intentionally not specified.
>
> Update the "Changes to underlying filesystems" section to note this
> restriction.  Move the paragraph describing the offline behavior below
> the online behavior so it is adjacent to the following 3 paragraphs
> describing the NFS export offline modification behavior.
>
> [1]: https://lore.kernel.org/linux-unionfs/20200708142353.GA103536@redhat.com/
> [2]: https://lore.kernel.org/linux-unionfs/CAOQ4uxi23Zsmfb4rCed1n=On0NNA5KZD74jjjeyz+et32sk-gg@mail.gmail.com/
> [3]: https://lore.kernel.org/linux-unionfs/20200817135651.GA637139@redhat.com/
> [4]: https://lore.kernel.org/linux-unionfs/20200709153616.GE150543@redhat.com/
> [5]: https://lore.kernel.org/linux-unionfs/20200812135529.GA122370@kevinolos/
>
> Signed-off-by: Kevin Locke <kevin@kevinlocke.name>

Thanks, applied.

Miklos

      parent reply	other threads:[~2020-10-30 13:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20 17:34 [PATCH] ovl: document lower modification caveats Kevin Locke
2020-08-23  2:22 ` [PATCH v2] " Kevin Locke
2020-09-22 12:18   ` Kevin Locke
2020-10-30 13:16   ` Miklos Szeredi [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='CAJfpegvakND7=_8eDdu9TAgXwYNN-vZi1pdY-gLzuF-Dn6C0_Q@mail.gmail.com' \
    --to=miklos@szeredi.hu \
    --cc=amir73il@gmail.com \
    --cc=kevin@kevinlocke.name \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=vgoyal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).