From: Trond Myklebust <Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
To: Al Viro <viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>,
Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH attempt=3 0/5] NFS private namespace patchset
Date: Sat, 20 Jun 2009 15:33:45 -0400 [thread overview]
Message-ID: <20090620193344.14142.22774.stgit@heimdal.trondhjem.org> (raw)
The following series is a resend of a set of patches that were
originally targetted for inclusion in 2.6.30-rc1. They build upon
Al Viro's "Cache root in nameidata" patches, and add the ability to
create a private mount namespace that is not visible to user
processes.
As stated before, the goal is to allow reuse of vfs_path_lookup() in
order to allow the nfs client to walk down NFSv4 mount paths, and locate
the directory that needs to be mounted.
This version of the patches uninlines the function put_mnt_ns() in order
to avoid the need to export vfsmount_lock, and merges it with
__put_mnt_ns().
Cheers
Trond
---
Trond Myklebust (5):
NFS: Correct the NFS mount path when following a referral
NFS: Fix nfs_path() to always return a '/' at the beginning of the path
NFSv4: Replace nfs4_path_walk() with VFS path lookup in a private namespace
VFS: Add VFS helper functions for setting up private namespaces
VFS: Uninline the function put_mnt_ns()
fs/namespace.c | 53 +++++++++--
fs/nfs/namespace.c | 5 +
fs/nfs/super.c | 202 +++++++++++++++++++++++++++++++++++++----
include/linux/mnt_namespace.h | 10 --
4 files changed, 231 insertions(+), 39 deletions(-)
--
Signature
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2009-06-20 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 19:33 Trond Myklebust [this message]
2009-06-20 19:33 ` [PATCH attempt=3 4/5] NFS: Fix nfs_path() to always return a '/' at the beginning of the path Trond Myklebust
[not found] ` <20090620193344.14142.22774.stgit-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-20 19:33 ` [PATCH attempt=3 2/5] VFS: Add VFS helper functions for setting up private namespaces Trond Myklebust
2009-06-20 19:33 ` [PATCH attempt=3 1/5] VFS: Uninline the function put_mnt_ns() Trond Myklebust
2009-06-20 19:33 ` [PATCH attempt=3 3/5] NFSv4: Replace nfs4_path_walk() with VFS path lookup in a private namespace Trond Myklebust
2009-06-20 19:33 ` [PATCH attempt=3 5/5] NFS: Correct the NFS mount path when following a referral Trond Myklebust
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=20090620193344.14142.22774.stgit@heimdal.trondhjem.org \
--to=trond.myklebust-hgovqubeegtqt0dzr+alfa@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.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).