linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-unionfs@vger.kernel.org
Subject: [PATCH 0/4] Overlayfs index features
Date: Tue, 24 Oct 2017 13:02:57 +0300	[thread overview]
Message-ID: <1508839381-24750-1-git-send-email-amir73il@gmail.com> (raw)

Miklos,

This series is an attempt not to repeat the mistakes of the past
w.r.t. overlayfs features.

I have given a lot of though about how to scale up with more
compat/incompat features instead of an ever growing disclaimer matrix
in overlafs/Kconfig.

My proposed solution only covers features compatibility among
sub-features of index or features which rely on index being enabled.
There is also a best effort attempt to impose features compatibility
as far as v3.18 using a trick with a dirty work dir.

Although this series is based on the stable fix patch "ovl: do not
cleanup unsupported index entries", it does NOT rely on the fix being
applied on v4.13 kernel for correct behavior on downgrade.

The first use case for incompat index features is going to be index=all
for NFS export - probably rocompat, not sure yet.

I don't think there is anything is this that should be backported
to v4.13 or rushed into v4.14.
What do you think?

Amir.

Amir Goldstein (4):
  ovl: introduce incompatible index feature
  ovl: declare index feature backward compatible
  ovl: cast a shadow of incomapt index into the past
  ovl: check incompat/rocompat index features

 fs/overlayfs/Kconfig     |  25 ++++++++---
 fs/overlayfs/dir.c       |  66 +++++++++++++++++++++++++++++
 fs/overlayfs/overlayfs.h |  20 ++++++++-
 fs/overlayfs/readdir.c   | 108 +++++++++++++++++++++++++++++++++++++++++++----
 fs/overlayfs/super.c     |  50 ++++++++++++++++++++--
 fs/overlayfs/util.c      | 105 +++++++++++++++++++++++++++++++++++++++++++++
 6 files changed, 354 insertions(+), 20 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-10-24 10:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 10:02 Amir Goldstein [this message]
2017-10-24 10:02 ` [PATCH 1/4] ovl: introduce incompatible index feature Amir Goldstein
2017-11-10 13:57   ` Vivek Goyal
2017-11-10 14:46     ` Amir Goldstein
2017-11-15 14:34       ` Vivek Goyal
2017-11-15 15:14         ` Amir Goldstein
2017-10-24 10:02 ` [PATCH 2/4] ovl: declare index feature backward compatible Amir Goldstein
2017-11-10 14:21   ` Vivek Goyal
2017-11-10 14:29     ` Amir Goldstein
2017-10-24 10:03 ` [PATCH 3/4] ovl: cast a shadow of incomapt index into the past Amir Goldstein
2017-11-10 14:53   ` Vivek Goyal
2017-11-10 16:30     ` Amir Goldstein
2017-10-24 10:03 ` [PATCH 4/4] ovl: check incompat/rocompat index features Amir Goldstein
2017-10-24 15:30 ` [PATCH 0/4] Overlayfs " 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=1508839381-24750-1-git-send-email-amir73il@gmail.com \
    --to=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).