linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Trond Myklebust
	<Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
Cc: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	Al Viro <viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>,
	Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/4] VFS: Add VFS helper functions for setting up private namespaces
Date: Fri, 19 Jun 2009 03:43:10 -0400	[thread overview]
Message-ID: <20090619074310.GA25197@infradead.org> (raw)
In-Reply-To: <1245361382.8756.47.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>

On Thu, Jun 18, 2009 at 02:43:02PM -0700, Trond Myklebust wrote:
> On Thu, 2009-06-18 at 16:55 -0400, Christoph Hellwig wrote:
> > On Thu, Jun 18, 2009 at 12:25:01PM -0700, Trond Myklebust wrote:
> > >  /* spinlock for vfsmount related operations, inplace of dcache_lock */
> > >  __cacheline_aligned_in_smp DEFINE_SPINLOCK(vfsmount_lock);
> > > +EXPORT_SYMBOL(vfsmount_lock);
> > 
> > This is not mentioned in the patch description and also doesn't seem
> > to be used in the following patches.
> > 
> > Exporting it is a really bad idea anyway as it protects data structures
> > that should not be exposed to filesystems.
> 
> It is used by the inlined function put_mnt_ns(). It would be trivial to
> make that an extern, and avoid the need for the vfsmount_lock export.
> Would that be acceptable?

I think moving it out of line is much better.  You can also merged it
into __put_mnt_ns while you're at it.

--
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

  parent reply	other threads:[~2009-06-19  7:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 19:25 [PATCH 0/4] NFS private namespace patchset Trond Myklebust
2009-06-18 19:25 ` [PATCH 3/4] NFS: Fix nfs_path() to always return a '/' at the beginning of the path Trond Myklebust
2009-06-18 19:25 ` [PATCH 2/4] NFSv4: Replace nfs4_path_walk() with VFS path lookup in a private namespace Trond Myklebust
     [not found] ` <20090618192500.19433.16770.stgit-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-18 19:25   ` [PATCH 4/4] NFS: Correct the NFS mount path when following a referral Trond Myklebust
2009-06-18 19:25   ` [PATCH 1/4] VFS: Add VFS helper functions for setting up private namespaces Trond Myklebust
2009-06-18 20:55     ` Christoph Hellwig
2009-06-18 21:43       ` Trond Myklebust
     [not found]         ` <1245361382.8756.47.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-19  7:43           ` Christoph Hellwig [this message]
2009-06-18 19:40   ` [PATCH 0/4] NFS private namespace patchset 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=20090619074310.GA25197@infradead.org \
    --to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
    --cc=Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@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).