linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Locke <kevin@kevinlocke.name>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-unionfs@vger.kernel.org,
	Amir Goldstein <amir73il@gmail.com>,
	Vivek Goyal <vgoyal@redhat.com>
Subject: [PATCH v2] ovl: document lower modification caveats
Date: Sat, 22 Aug 2020 20:22:57 -0600	[thread overview]
Message-ID: <fe78446e6565cda29cc2c87f3e3c1b2a16f5d5cc.1598149357.git.kevin@kevinlocke.name> (raw)
In-Reply-To: <82b537e0ca5fa38b492413bd665c0198e6761015.1597944769.git.kevin@kevinlocke.name>

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>
---

Changes since v1:
- Actually send to the maintainer this time.
  (Sorry Miklos Szeredi, not sure what I was thinking on v1!)
- Rebase onto overlayfs-next of
  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git

As mentioned with v1, I'm still open to collaborating on a combined
patch if there is still interest in including Vivek's changes to the
"Sharing and copying layers" section.

This patch does not mention nfs_export being incompatible with offline
changes to lower, since the following 3 paragraphs specify the behavior
(IIUC).  If the behavior of offline modification with nfs_export is
undefined, should these paragraphs be removed?

Thanks for considering (again),
Kevin

 Documentation/filesystems/overlayfs.rst | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/Documentation/filesystems/overlayfs.rst b/Documentation/filesystems/overlayfs.rst
index fcda5d6ba9ac..9b39374afdbd 100644
--- a/Documentation/filesystems/overlayfs.rst
+++ b/Documentation/filesystems/overlayfs.rst
@@ -467,14 +467,18 @@ summarized in the `Inode properties`_ table above.
 Changes to underlying filesystems
 ---------------------------------
 
-Offline changes, when the overlay is not mounted, are allowed to either
-the upper or the lower trees.
-
 Changes to the underlying filesystems while part of a mounted overlay
 filesystem are not allowed.  If the underlying filesystem is changed,
 the behavior of the overlay is undefined, though it will not result in
 a crash or deadlock.
 
+Offline changes, when the overlay is not mounted, are allowed to the
+upper tree.  Offline changes to the lower tree are only allowed if the
+"metadata only copy up", "inode index", and "redirect_dir" features
+have not been used.  If the lower tree is modified and any of these
+features has been used, the behavior of the overlay is undefined,
+though it will not result in a crash or deadlock.
+
 When the overlay NFS export feature is enabled, overlay filesystems
 behavior on offline changes of the underlying lower layer is different
 than the behavior when NFS export is disabled.
-- 
2.28.0


  reply	other threads:[~2020-08-23  2:23 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 ` Kevin Locke [this message]
2020-09-22 12:18   ` [PATCH v2] " Kevin Locke
2020-10-30 13:16   ` Miklos Szeredi

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=fe78446e6565cda29cc2c87f3e3c1b2a16f5d5cc.1598149357.git.kevin@kevinlocke.name \
    --to=kevin@kevinlocke.name \
    --cc=amir73il@gmail.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --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).