From: Miklos Szeredi <miklos@szeredi.hu>
To: Andy Whitcroft <apw@canonical.com>
Cc: Serge Hallyn <serge.hallyn@ubuntu.com>,
Neil Brown <neilb@suse.de>,
linux-unionfs@vger.kernel.org,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: How to cope with two incompatible overlayfs formats out in the wild
Date: Tue, 18 Nov 2014 15:28:03 +0100 [thread overview]
Message-ID: <CAJfpegtG68g=dDi7j-WfhkuJidZRBg46vyuWg8CTrW3TrW_nYw@mail.gmail.com> (raw)
[CC-ing mailing lists, Al and Linus for wider exposure]
This issue is this: Ubuntu and SUSE carry an "old" format of overlayfs
while mainline has a "new" format. The differences are:
- whiteouts are represented differently (symlink + xattr in the old
format, chardev in the new)
- new one needs a "workdir" mount option, which points to a directory
on the same filesystem as upperdir. If upperdir was the root of the
filesystem then it needs to be moved into a subdir to make space for
the work directory.
Migrating from old to new is not a big issue, but Ubuntu people have
expressed concerns about systems with mixed kernel versions and want
to support the old format alongside the new.
This can all be done with out-of-tree code.
So from mainline we need two things:
- when mounting distinguish between old and new format.
- userspace can detect which formats are supported by the kernel.
If we'd have a different filesystem type for the old and new formats,
then that would solve both (checking /proc/filesystems would indicate
which one is supported).
Unfortunately that would mean having to change "overlayfs" type to
something else in 3.18. Question is, is there some sane name which
would fit? "overlayfs2" is perhaps the best, but I'm not overly
enthusiastic about it.
Any other ideas?
Thanks,
Miklos
next reply other threads:[~2014-11-18 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 14:28 Miklos Szeredi [this message]
2014-11-18 17:07 ` How to cope with two incompatible overlayfs formats out in the wild Andy Whitcroft
2014-11-19 1:59 ` Al Viro
2014-11-19 8:19 ` Miklos Szeredi
2014-11-19 14:29 ` 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='CAJfpegtG68g=dDi7j-WfhkuJidZRBg46vyuWg8CTrW3TrW_nYw@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=apw@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=serge.hallyn@ubuntu.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).