linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Blunck <jblunck@suse.de>
To: viro@ZenIV.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	vaurora@redhat.com, hch@lst.de, miklos@szeredi.hu
Subject: [PATCH] Preparation work for VFS based union mounts
Date: Wed, 17 Jun 2009 22:45:04 +0200	[thread overview]
Message-ID: <1245271510-31542-1-git-send-email-jblunck@suse.de> (raw)

Al,
here are some patches that are indenpendant from but necessary for the union
mount patch set. Valerie and I think they are ok to go in separately from the
rest of the patches.

Thanks,
Jan

Jan Blunck (6):
  VFS: BUG() if somebody tries to rehash an already hashed dentry
  VFS: propagate mnt_flags into do_loopback
  VFS: Make lookup_hash() return a struct path
  VFS: Remove unnecessary micro-optimization in cached_lookup()
  VFS: Make real_lookup() return a struct path
  VFS: Introduce dput() variant that maintains a kill-list

 fs/dcache.c    |  116 ++++++++++++++++++++++++++++---
 fs/namei.c     |  209 +++++++++++++++++++++++++++++++-------------------------
 fs/namespace.c |    7 +-
 3 files changed, 225 insertions(+), 107 deletions(-)


             reply	other threads:[~2009-06-17 20:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 20:45 Jan Blunck [this message]
2009-06-17 20:45 ` [PATCH] VFS: BUG() if somebody tries to rehash an already hashed dentry Jan Blunck
2009-06-17 20:45 ` [PATCH] VFS: propagate mnt_flags into do_loopback Jan Blunck
2009-06-17 20:45 ` [PATCH] VFS: Make lookup_hash() return a struct path Jan Blunck
2009-06-18 11:19   ` James Morris
2009-06-17 20:45 ` [PATCH] VFS: Remove unnecessary micro-optimization in cached_lookup() Jan Blunck
2009-06-17 20:45 ` [PATCH] VFS: Make real_lookup() return a struct path Jan Blunck
2009-06-18 11:21   ` James Morris
2009-06-17 20:45 ` [PATCH] VFS: Introduce dput() variant that maintains a kill-list Jan Blunck
2009-06-18 11:30   ` James Morris

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=1245271510-31542-1-git-send-email-jblunck@suse.de \
    --to=jblunck@suse.de \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=vaurora@redhat.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).