From: Al Viro <viro@ZenIV.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
apw@canonical.com, nbd@openwrt.org, neilb@suse.de,
hramrach@centrum.cz, jordipujolp@gmail.com,
ezk@fsl.cs.sunysb.edu, ricwheeler@gmail.com, dhowells@redhat.com,
hpj@urpla.net, sedat.dilek@googlemail.com, penberg@kernel.org,
mszeredi@suse.cz
Subject: Re: [PATCH 0/8] overlay filesystem: request for inclusion
Date: Fri, 5 Aug 2011 00:11:34 +0100 [thread overview]
Message-ID: <20110804231134.GO2203@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1312462417-8826-1-git-send-email-miklos@szeredi.hu>
On Thu, Aug 04, 2011 at 02:53:29PM +0200, Miklos Szeredi wrote:
> Al, Linus and all interested parties,
>
> Here's the latest version of overlayfs.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs.v11
>
> I think it's been merge-ready for some time and has gotten a fair
> amount of attention and testing from various parties. Yet,
> apparently, it isn't getting closer to being merged.
>
> There's union-mounts which has a very similar feature set, if a
> completely different implementation, but that also is not being
> considered yet for merge.
>
> So, Al, can you please share your thougths?
Simple: please, *please* hold back until we have atomic_open mess sorted
out. I'm fucking sick and tired of playing whack-a-mole in that area -
for nearly three years by now; we fortunately are very close to getting
this shit done right - the main remaining obstacle is ->d_revalidate()
abuse by NFS and I seriously hope to get it over and done with in a week or so.
Once that is done and the damn thing is in #for-next, I'll ping you, dhowells
and probably aufs folks to start sorting this out, so that we would have that
finished before 3.2 opens.
next prev parent reply other threads:[~2011-08-04 23:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 12:53 [PATCH 0/8] overlay filesystem: request for inclusion Miklos Szeredi
2011-08-04 12:53 ` [PATCH 1/8] vfs: add i_op->open() Miklos Szeredi
2011-08-04 12:53 ` [PATCH 2/8] vfs: export do_splice_direct() to modules Miklos Szeredi
2011-08-04 12:53 ` [PATCH 3/8] vfs: introduce clone_private_mount() Miklos Szeredi
2011-08-04 12:53 ` [PATCH 4/8] overlay filesystem Miklos Szeredi
2011-08-04 12:53 ` [PATCH 5/8] overlayfs: add statfs support Miklos Szeredi
2011-08-04 12:53 ` [PATCH 6/8] overlayfs: implement show_options Miklos Szeredi
2011-08-04 12:53 ` [PATCH 7/8] overlay: overlay filesystem documentation Miklos Szeredi
2011-08-04 12:53 ` [PATCH 8/8] fs: limit filesystem stacking depth Miklos Szeredi
2011-08-04 12:58 ` [PATCH 0/8] overlay filesystem: request for inclusion Pekka Enberg
2011-08-04 23:11 ` Al Viro [this message]
2011-08-05 9:11 ` 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=20110804231134.GO2203@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=dhowells@redhat.com \
--cc=ezk@fsl.cs.sunysb.edu \
--cc=hpj@urpla.net \
--cc=hramrach@centrum.cz \
--cc=jordipujolp@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@suse.cz \
--cc=nbd@openwrt.org \
--cc=neilb@suse.de \
--cc=penberg@kernel.org \
--cc=ricwheeler@gmail.com \
--cc=sedat.dilek@googlemail.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).