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: Amir Goldstein <amir73il@gmail.com>, linux-unionfs@vger.kernel.org
Subject: [PATCH] ovl: add xino to "changes to underlying fs" docs
Date: Mon,  8 Mar 2021 08:23:16 -0700	[thread overview]
Message-ID: <b36a429d7c563730c28d763d4d57a6fc30508a4f.1615216996.git.kevin@kevinlocke.name> (raw)
In-Reply-To: <CAOQ4uxj4zNHU49Q6JeUrw4dvgRBumzhtvGXpuG4WDEi5G7uyxw@mail.gmail.com>

Add "xino" to the list of features which cause undefined behavior for
offline changes to the lower tree in the "Changes to underlying
filesystems" section of the documentation to make users aware of
potential issues if the lower tree is modified and xino was enabled.

This omission was noticed by Amir Goldstein, who mentioned that xino is
one of the "forbidden" features for making offline changes to the lower
tree and that it wasn't currently documented.

Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
---
 Documentation/filesystems/overlayfs.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/filesystems/overlayfs.rst b/Documentation/filesystems/overlayfs.rst
index 78240e29b0bb..52d47bed9ef8 100644
--- a/Documentation/filesystems/overlayfs.rst
+++ b/Documentation/filesystems/overlayfs.rst
@@ -476,9 +476,9 @@ 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,
+"metadata only copy up", "inode index", "redirect_dir", and "xino"
+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
-- 
2.30.1


       reply	other threads:[~2021-03-08 15:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOQ4uxj4zNHU49Q6JeUrw4dvgRBumzhtvGXpuG4WDEi5G7uyxw@mail.gmail.com>
2021-03-08 15:23 ` Kevin Locke [this message]
2021-03-08 17:41   ` [PATCH] ovl: add xino to "changes to underlying fs" docs Amir Goldstein
2021-03-08 23:49     ` Kevin Locke
2021-03-09  7:24       ` Amir Goldstein
2021-03-09 14:29         ` Amir Goldstein
2021-03-09 17:43         ` Kevin Locke
2021-03-09 18:50         ` Vivek Goyal
2021-03-09 19:24           ` 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=b36a429d7c563730c28d763d4d57a6fc30508a4f.1615216996.git.kevin@kevinlocke.name \
    --to=kevin@kevinlocke.name \
    --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 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).