From: Al Viro <viro@ZenIV.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Andy Whitcroft <apw@canonical.com>,
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>
Subject: Re: How to cope with two incompatible overlayfs formats out in the wild
Date: Wed, 19 Nov 2014 01:59:08 +0000 [thread overview]
Message-ID: <20141119015908.GV7996@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAJfpegtG68g=dDi7j-WfhkuJidZRBg46vyuWg8CTrW3TrW_nYw@mail.gmail.com>
On Tue, Nov 18, 2014 at 03:28:03PM +0100, Miklos Szeredi wrote:
> 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?
Umm... What does the old one do when it sees workdir=<something> in the
options?
next prev parent reply other threads:[~2014-11-19 1:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 14:28 How to cope with two incompatible overlayfs formats out in the wild Miklos Szeredi
2014-11-18 17:07 ` Andy Whitcroft
2014-11-19 1:59 ` Al Viro [this message]
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=20141119015908.GV7996@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=apw@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=neilb@suse.de \
--cc=serge.hallyn@ubuntu.com \
--cc=torvalds@linux-foundation.org \
/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).