linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valerie Aurora <vaurora@redhat.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
Subject: [RFC PATCH 0/4] union mounts: In-kernel copyup v1
Date: Tue, 30 Mar 2010 14:16:53 -0700	[thread overview]
Message-ID: <1269983817-3252-1-git-send-email-vaurora@redhat.com> (raw)

Well, not really v1, but gotta start numbering somewhere. :)

This is a proof of concept implementation of in-kernel copyup for
union mounts.  It implements copy up of files on chown(), which is in
some ways harder than rename() or link() because it doesn't lookup the
parent separately.

The idea behind this version is to keep the <mnt,dentry> pair of the
parent directory of the chown() target around in case we need to copy
it up.  If we do need to copy up, we already have the path of the
directory for the topmost file system, instead of having to look it up
again.

Valerie Aurora (4):
  VFS: Split inode_permission() and create path_permission()
  VFS: create user_path_and_parent()
  union-mount: In-kernel copyup routines
  union-mount: Implement chown()

 fs/namei.c            |  125 +++++++++++++++++++++++++++++++----
 fs/open.c             |   33 ++++++++--
 fs/union.c            |  172 +++++++++++++++++++++++++++++++++++++++++++++++++
 include/linux/fs.h    |    1 +
 include/linux/namei.h |    2 +
 include/linux/union.h |    2 +
 6 files changed, 315 insertions(+), 20 deletions(-)


             reply	other threads:[~2010-03-30 21:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 21:16 Valerie Aurora [this message]
2010-03-30 21:16 ` [PATCH 1/4] VFS: Split inode_permission() and create path_permission() Valerie Aurora
2010-03-30 21:16   ` [PATCH 2/4] VFS: create user_path_and_parent() Valerie Aurora
2010-03-30 21:16     ` [PATCH 3/4] union-mount: In-kernel copyup routines Valerie Aurora
2010-03-30 21:16       ` [PATCH 4/4] union-mount: Implement chown() 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=1269983817-3252-1-git-send-email-vaurora@redhat.com \
    --to=vaurora@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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).