From: Josef "Jeff" Sipek <jsipek@cs.sunysb.edu>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org,
hch@infradead.org, viro@ftp.linux.org.uk
Subject: [PATCH 0 of 23] Unionfs: Stackable Namespace Unification Filesystem
Date: Sat, 07 Oct 2006 01:07:19 -0400 [thread overview]
Message-ID: <patchbomb.1160197639@thor.fsl.cs.sunysb.edu> (raw)
This set of patches constitutes Unionfs version 2.0. We are presenting it to
be reviewed and considered for inclusion into the kernel.
Some of the comments addressed since the first submission are:
- unionfs_lookup must pass lookup intents to the lower filesystem (Trond
Myklebust)
- patches reordered (Stephen Rothwell)
- numerous style comments by Jan Engelhardt
Note that this set of patches contains a considerably trimmed-down version
of Unionfs. That way it'd be possible to evaluate Unionfs's most basic
functionality, gradually adding features in future patches.
To download tarballs of the full source, along with userspace utilities,
read various documents and other info about Unionfs, see the home page at
<http://www.unionfs.org>
Josef "Jeff" Sipek, on behalf of the Unionfs team.
Index:
=======
[PATCH 1 of 23] Unionfs: Documentation
[PATCH 2 of 23] lookup_one_len_nd - lookup_one_len with nameidata
[PATCH 3 of 23] Unionfs: Branch management functionality
[PATCH 4 of 23] Unionfs: Common file operations
[PATCH 5 of 23] Unionfs: Copyup Functionality
[PATCH 6 of 23] Unionfs: Dentry operations
[PATCH 7 of 23] Unionfs: File operations
[PATCH 8 of 23] Unionfs: Directory file operations
[PATCH 9 of 23] Unionfs: Directory manipulation helper functions
[PATCH 10 of 23] Unionfs: Inode operations
[PATCH 11 of 23] Unionfs: Lookup helper functions
[PATCH 12 of 23] Unionfs: Main module functions
[PATCH 13 of 23] Unionfs: Readdir state
[PATCH 14 of 23] Unionfs: Rename
[PATCH 15 of 23] Unionfs: Privileged operations workqueue
[PATCH 16 of 23] Unionfs: Handling of stale inodes
[PATCH 17 of 23] Unionfs: Miscellaneous helper functions
[PATCH 18 of 23] Unionfs: Superblock operations
[PATCH 19 of 23] Unionfs: Helper macros/inlines
[PATCH 20 of 23] Unionfs: Internal include file
[PATCH 21 of 23] Unionfs: Include file
[PATCH 22 of 23] Unionfs: Unlink
[PATCH 23 of 23] Unionfs: Kconfig and Makefile
Known Issues and Limitations:
- The NFS server returns -EACCES for read-only exports, instead of -EROFS.
This means we can't reliably detect a read-only NFS export.
- Modifying a Unionfs branch directly, while the union is mounted, is
currently unsupported. Any such change may cause Unionfs to oops and it
can even result in data loss!
- Unionfs shouldn't use lookup_one_len on the underlying fs as it confuses
NFS. Currently, unionfs_lookup passes lookup intents to the lower
filesystem, this eliminates part of the problem. The remaining calls to
lookup_one_len may need to be changed to pass an intent.
For the initial release we removed support for xattrs, persistent inode
mappings, and mmap operations.
Signed-off-by: Josef "Jeff" Sipek <jsipek@cs.sunysb.edu>
Signed-off-by: David Quigley <dquigley@fsl.cs.sunysb.edu>
Signed-off-by: Erez Zadok <ezk@cs.sunysb.edu>
next reply other threads:[~2006-10-07 5:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-07 5:07 Josef Jeff Sipek [this message]
2006-10-07 5:07 ` [PATCH 1 of 23] Unionfs: Documentation Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 2 of 23] lookup_one_len_nd - lookup_one_len with nameidata argument Josef Jeff Sipek
2006-10-07 17:03 ` Daniel Walker
2006-10-07 18:23 ` Josef Sipek
2006-10-07 18:37 ` Daniel Walker
2006-10-07 5:07 ` [PATCH 3 of 23] Unionfs: Branch management functionality Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 4 of 23] Unionfs: Common file operations Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 5 of 23] Unionfs: Copyup Functionality Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 6 of 23] Unionfs: Dentry operations Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 7 of 23] Unionfs: File operations Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 8 of 23] Unionfs: Directory file operations Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 9 of 23] Unionfs: Directory manipulation helper functions Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 10 of 23] Unionfs: Inode operations Josef Jeff Sipek
2006-10-13 8:53 ` Pekka Enberg
2006-10-07 5:07 ` [PATCH 11 of 23] Unionfs: Lookup helper functions Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 12 of 23] Unionfs: Main module functions Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 13 of 23] Unionfs: Readdir state Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 14 of 23] Unionfs: Rename Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 15 of 23] Unionfs: Privileged operations workqueue Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 16 of 23] Unionfs: Handling of stale inodes Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 17 of 23] Unionfs: Miscellaneous helper functions Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 18 of 23] Unionfs: Superblock operations Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 19 of 23] Unionfs: Helper macros/inlines Josef Jeff Sipek
2006-10-13 8:23 ` Pekka Enberg
2006-10-07 5:07 ` [PATCH 20 of 23] Unionfs: Internal include file Josef Jeff Sipek
2006-10-13 8:02 ` Pekka Enberg
2006-10-13 8:05 ` Pekka Enberg
2006-10-07 5:07 ` [PATCH 21 of 23] Unionfs: Include file Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 22 of 23] Unionfs: Unlink Josef Jeff Sipek
2006-10-07 5:07 ` [PATCH 23 of 23] Unionfs: Kconfig and Makefile Josef Jeff Sipek
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=patchbomb.1160197639@thor.fsl.cs.sunysb.edu \
--to=jsipek@cs.sunysb.edu \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@ftp.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).