From: Valerie Aurora <vaurora@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: David Woodhouse <dwmw2@infradead.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jan Blunck <jblunck@suse.de>,
Christoph Hellwig <hch@infradead.org>,
Andy Whitcroft <apw@canonical.com>,
Scott James Remnant <scott@canonical.com>,
Sandu Popa Marius <sandupopamarius@gmail.com>,
Jan Rekorajski <baggins@sith.mimuw.edu.pl>,
"J. R. Okajima" <hooanon05@yahoo.co.jp>,
Arnd Bergmann <arnd@arndb.de>,
Vladimir Dronnikov <dronnikov@gmail.com>,
Felix Fietkau <nbd@openwrt.org>
Subject: Fallthrus as full-length symlinks?
Date: Fri, 13 Nov 2009 12:46:31 -0500 [thread overview]
Message-ID: <20091113174631.GD19656@shell> (raw)
Fallthrus were invented as a placeholders for readdir() on a
union-mounted directory - basically, to use the top-level file
system's readdir() cookie mechanism. Fallthrus are persistent
directory entries and are implemented by the underlying file system -
such as ext2 or tmpfs - in whatever way it sees fit. We've
implemented them for ext2 in two ways: as a regular directory entry
with a magic inode number, and as a regular directory entry with a
special file type.
Recently, David Woodhouse suggested implementing fallthrus as
full-length symlinks with a special flag. The interesting thing about
this idea is that it could theoretically let us rename a file from the
low level file system to another place in the low-level file system
without copying the contents of the file up. Basically, we can
arbitrarily swizzle the namespace of the low-level by maintaining a
set of symlinks above.
Is this useful? Is it implementable?
Background reading:
http://valerieaurora.org/union/
-VAL
next reply other threads:[~2009-11-13 17:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 17:46 Valerie Aurora [this message]
2009-11-13 18:46 ` Fallthrus as full-length symlinks? Erez Zadok
2009-11-13 19:55 ` Arnd Bergmann
2009-11-17 19:06 ` Valerie Aurora
2009-11-17 19:13 ` Valerie Aurora
2009-11-17 19:18 ` David Woodhouse
2009-11-17 19:43 ` Valerie Aurora
2009-11-17 20:20 ` Erez Zadok
2009-11-23 18:26 ` Valerie Aurora
2009-11-23 18:44 ` Arnd Bergmann
2009-11-25 2:12 ` Valerie Aurora
2009-11-24 11:18 ` Miklos Szeredi
2009-11-18 5:47 ` hooanon05
2009-11-25 2:15 ` Valerie Aurora
2009-11-25 2:36 ` hooanon05
2009-11-25 9:43 ` David Woodhouse
[not found] <62b7cf460911151915k12c57c6dne9b49399bd8ce9d5@mail.gmail.com>
2009-11-17 0:57 ` AYAN TYAGI
2009-11-17 6:44 ` Jamie Lokier
2009-11-17 8:03 ` AYAN TYAGI
2009-11-17 19:47 ` Valerie Aurora
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=20091113174631.GD19656@shell \
--to=vaurora@redhat.com \
--cc=apw@canonical.com \
--cc=arnd@arndb.de \
--cc=baggins@sith.mimuw.edu.pl \
--cc=dronnikov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=hch@infradead.org \
--cc=hooanon05@yahoo.co.jp \
--cc=jblunck@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=sandupopamarius@gmail.com \
--cc=scott@canonical.com \
--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).