From: Theodore Ts'o <tytso@mit.edu>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Overlays and file(system) unioning issues
Date: Tue, 28 Jul 2015 08:16:41 -0400 [thread overview]
Message-ID: <20150728121641.GI2851@thunk.org> (raw)
In-Reply-To: <CAJfpegvuaOFm+pN4Gec0h13XaHAtOtia2Ww1TN+gCuVkZVcECw@mail.gmail.com>
On Tue, Jul 28, 2015 at 09:13:18AM +0200, Miklos Szeredi wrote:
>
> Exactly. Switching overlayfs to deal with DT_WHT is trivial.
> Turning off backward compatibility (checking 0,0 chardev as internal
> representation) can be made a mount option of overlayfs. If the
> DT_WHT representation is used, then it will work either way, but will
> be suboptimal due to getattr on chardev. If the back compatibility
> is turned off then it will be optimal, but wouldn't deal with the old
> representation.
>
> The only remaining issue being backward incompatibility of the
> filesystem image itself (old fsck, ...). Whether that's a problem or
> not is up to the user/distro to decide.
Yep, this seems like a no-brainer. Given that, is there anything that
requires discussion at the Kernel Summit?
- Ted
next prev parent reply other threads:[~2015-07-28 12:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 16:01 David Howells
2015-07-24 16:10 ` David Howells
2015-07-24 16:58 ` Eric W. Biederman
2015-07-24 17:12 ` James Bottomley
2015-07-25 15:39 ` Lai Jiangshan
2015-07-29 13:36 ` Serge E. Hallyn
2015-07-27 13:19 ` David Woodhouse
2015-07-27 14:33 ` Theodore Ts'o
2015-07-28 7:13 ` Miklos Szeredi
2015-07-28 12:16 ` Theodore Ts'o [this message]
2015-10-15 19:49 ` David Howells
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=20150728121641.GI2851@thunk.org \
--to=tytso@mit.edu \
--cc=ksummit-discuss@lists.linuxfoundation.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