From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Jeff Layton <jlayton@poochiereds.net>,
"J . Bruce Fields" <bfields@fieldses.org>,
linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH v2 06/17] ovl: copy up before encoding dir file handle when ofs->numlower > 1
Date: Thu, 4 Jan 2018 19:20:38 +0200 [thread overview]
Message-ID: <1515086449-26563-7-git-send-email-amir73il@gmail.com> (raw)
In-Reply-To: <1515086449-26563-1-git-send-email-amir73il@gmail.com>
Decoding a merge dir, whose origin's parent may be on a different lower
layer then the overlay parent's origin is not implemented. As a simple
aproximation, we do not encode lower dir file handles when overlay has
multiple lower layers. Instead, we copy up the lower dir first and then
encode an upper dir file handle.
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---
fs/overlayfs/export.c | 66 +++++++++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 64 insertions(+), 2 deletions(-)
diff --git a/fs/overlayfs/export.c b/fs/overlayfs/export.c
index 919d43aaa387..149cfb5c967e 100644
--- a/fs/overlayfs/export.c
+++ b/fs/overlayfs/export.c
@@ -26,13 +26,48 @@
* copied up before NFS export was enabled. In that case we don't need to worry
* about staying consistent with pre copy up encoding and we encode an upper
* file handle.
+ *
+ * The following table summarizes the different file handle encodings used for
+ * different overlay object types with overlay configuration of single and
+ * multiple lower layers:
+ *
+ * Object type | Single lower | Multiple lower
+ * --------------------------------------------------------
+ * Pure upper | U | U
+ * Non-indexed upper | U | U
+ * Indexed non-dir | L | L
+ * Lower non-dir | L | L
+ * Indexed directory | L | U
+ * Lower directory | L | U (*)
+ *
+ * U = upper file handle
+ * L = lower file handle
+ *
+ * The important thing to note is that within the same overlay configuration
+ * an overlay object encoding is invariant to copy up (i.e. Lower->Indexed).
+ *
+ * (*) If decoding an overlay dir from origin is not implemented, we do not
+ * encode by lower inode, because if file gets copied up after we encoded it,
+ * we won't be able to decode the file handle. To mitigate this case, we copy
+ * up the lower dir first and then encode an upper dir file handle.
*/
static bool ovl_should_encode_origin(struct dentry *dentry)
{
+ struct ovl_fs *ofs = dentry->d_sb->s_fs_info;
+
/* Root dentry was born upper */
if (dentry == dentry->d_sb->s_root)
return false;
+ /*
+ * Decoding a merge dir, whose origin's parent may be on a different
+ * lower layer then the overlay parent's origin is not implemented.
+ * As a simple aproximation, we do not encode lower dir file handles
+ * when overlay has multiple lower layers.
+ */
+ if (d_is_dir(dentry) && ofs->numlower > 1)
+ return false;
+
/* Decoding a non-indexed upper from origin is not implemented */
if (ovl_dentry_upper(dentry) &&
!ovl_test_flag(OVL_INDEX, d_inode(dentry)))
@@ -41,16 +76,43 @@ static bool ovl_should_encode_origin(struct dentry *dentry)
return true;
}
+static int ovl_encode_maybe_copy_up(struct dentry *dentry)
+{
+ int err;
+
+ if (ovl_dentry_upper(dentry))
+ return 0;
+
+ err = ovl_want_write(dentry);
+ if (err)
+ return err;
+
+ err = ovl_copy_up(dentry);
+
+ ovl_drop_write(dentry);
+ return err;
+}
+
int ovl_d_to_fh(struct dentry *dentry, char *buf, int buflen)
{
- struct dentry *upper = ovl_dentry_upper(dentry);
+ struct dentry *upper;
struct dentry *origin = ovl_dentry_lower(dentry);
struct ovl_fh *fh = NULL;
int err;
- if (!ovl_should_encode_origin(dentry))
+ /*
+ * If we should not encode a lower dir file handle, copy up and encode
+ * an upper dir file handle.
+ */
+ if (!ovl_should_encode_origin(dentry)) {
+ err = ovl_encode_maybe_copy_up(dentry);
+ if (err)
+ goto fail;
+
origin = NULL;
+ }
+ upper = ovl_dentry_upper(dentry);
err = -EACCES;
if (!upper || origin)
goto fail;
--
2.7.4
next prev parent reply other threads:[~2018-01-04 17:20 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 17:20 [PATCH v2 00/17] Overlayfs NFS export support Amir Goldstein
2018-01-04 17:20 ` [PATCH v2 01/17] ovl: document NFS export Amir Goldstein
2018-01-11 16:06 ` Miklos Szeredi
2018-01-11 16:26 ` Amir Goldstein
2018-01-12 15:43 ` Miklos Szeredi
2018-01-12 15:49 ` Miklos Szeredi
2018-01-12 18:50 ` Amir Goldstein
2018-01-13 8:54 ` Amir Goldstein
2018-01-04 17:20 ` [PATCH v2 02/17] ovl: encode pure upper file handles Amir Goldstein
2018-01-18 10:31 ` Miklos Szeredi
2018-01-04 17:20 ` [PATCH v2 03/17] ovl: decode " Amir Goldstein
2018-01-18 14:09 ` Miklos Szeredi
2018-01-18 14:34 ` Amir Goldstein
2018-01-18 14:39 ` Miklos Szeredi
2018-01-18 19:49 ` Amir Goldstein
2018-01-18 20:10 ` Miklos Szeredi
2018-01-18 20:35 ` Amir Goldstein
2018-01-18 22:57 ` Amir Goldstein
2018-01-19 0:23 ` Amir Goldstein
2018-01-19 10:39 ` Miklos Szeredi
2018-01-19 11:07 ` Amir Goldstein
2018-01-19 20:10 ` Amir Goldstein
2018-01-24 10:34 ` Miklos Szeredi
2018-01-24 11:04 ` Amir Goldstein
2018-01-24 11:18 ` Amir Goldstein
2018-01-24 11:55 ` Amir Goldstein
2018-01-04 17:20 ` [PATCH v2 04/17] ovl: decode connected upper dir " Amir Goldstein
2018-01-05 12:33 ` Amir Goldstein
2018-01-05 15:18 ` J . Bruce Fields
2018-01-05 15:34 ` Amir Goldstein
2018-01-15 11:41 ` Miklos Szeredi
2018-01-15 11:33 ` Miklos Szeredi
2018-01-15 12:20 ` Amir Goldstein
2018-01-15 14:56 ` Miklos Szeredi
2018-01-17 11:18 ` Amir Goldstein
2018-01-17 12:20 ` Amir Goldstein
2018-01-17 13:29 ` Amir Goldstein
2018-01-17 15:42 ` Miklos Szeredi
2018-01-17 16:34 ` Amir Goldstein
2018-01-17 21:36 ` Amir Goldstein
2018-01-18 8:22 ` Miklos Szeredi
2018-01-18 8:47 ` Amir Goldstein
2018-01-18 9:12 ` Miklos Szeredi
2018-01-18 10:28 ` Amir Goldstein
2018-01-04 17:20 ` [PATCH v2 05/17] ovl: encode non-indexed upper " Amir Goldstein
2018-01-15 11:58 ` Miklos Szeredi
2018-01-15 12:07 ` Amir Goldstein
2018-01-04 17:20 ` Amir Goldstein [this message]
2018-01-04 17:20 ` [PATCH v2 07/17] ovl: encode lower " Amir Goldstein
2018-01-04 17:20 ` [PATCH v2 08/17] ovl: decode lower non-dir " Amir Goldstein
2018-01-04 17:20 ` [PATCH v2 09/17] ovl: decode indexed " Amir Goldstein
2018-01-18 13:11 ` Miklos Szeredi
2018-01-04 17:20 ` [PATCH v2 10/17] ovl: decode lower file handles of unlinked but open files Amir Goldstein
2018-01-16 9:16 ` Miklos Szeredi
2018-01-16 9:37 ` Amir Goldstein
2018-01-16 10:10 ` Miklos Szeredi
2018-01-16 10:40 ` Amir Goldstein
2018-01-16 11:07 ` Miklos Szeredi
2018-01-17 21:05 ` Amir Goldstein
2018-01-18 14:18 ` Amir Goldstein
2018-02-27 11:35 ` Amir Goldstein
2018-01-04 17:20 ` [PATCH v2 11/17] ovl: decode indexed dir file handles Amir Goldstein
2018-01-04 17:20 ` [PATCH v2 12/17] ovl: decode pure lower " Amir Goldstein
2018-01-04 17:20 ` [PATCH v2 13/17] ovl: hash directory inodes for NFS export Amir Goldstein
2018-01-04 17:20 ` [PATCH v2 14/17] ovl: lookup connected ancestor of dir in inode cache Amir Goldstein
2018-01-04 17:20 ` [PATCH v2 15/17] ovl: lookup indexed ancestor of lower dir Amir Goldstein
2018-01-04 17:20 ` [PATCH v2 16/17] ovl: wire up NFS export support Amir Goldstein
2018-01-04 17:20 ` [PATCH v2 17/17] nfsd: encode stat->mtime for getattr instead of inode->i_mtime 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=1515086449-26563-7-git-send-email-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=bfields@fieldses.org \
--cc=jlayton@poochiereds.net \
--cc=linux-fsdevel@vger.kernel.org \
--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 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.