public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Waychison <mikew@google.com>
To: coywolf@sosdg.org
Cc: akpm@osdl.org, bunk@stusta.de, linux-kernel@vger.kernel.org
Subject: Re: [patch] unexport __mntput()
Date: Sun, 14 Aug 2005 21:07:06 -0700	[thread overview]
Message-ID: <430014EA.4030404@google.com> (raw)
In-Reply-To: <20050815015357.GA16778@everest.sosdg.org>

Coywolf Qi Hunt wrote:
> Hello,
> 
> Unexport __mntput() was talked about two months ago. http://lkml.org/lkml/2005/6/9/69
> Modules should not call __mntput() directly. If autofs or nfsd does that, it's
>  being wrong.

I think you missed the point in the last discussion.  __mntput is called 
from mntput(), which autofs and nfsd call.  Their use is correct given 
what they do:

Autofs 3 and 4 use it for walking the vfsmount tree and determining 
if/when a mountpoint is ready to expire.

Nfsd uses it to serve up nfs exports that don't cross mountpoints (or 
do, if "crossmnt" is specified in /etc/exports.

Thanks,

Mike Waychison

> 
> 		Coywolf
> 
> 
> Signed-off-by: Coywolf Qi Hunt <coywolf@sosdg.org>
> --- 2.6.13-rc6/fs/namespace.c~unexport-__mntput	2005-08-12 08:21:22.000000000 -0500
> +++ 2.6.13-rc6/fs/namespace.c	2005-08-14 20:32:01.000000000 -0500
> @@ -180,8 +180,6 @@
>  	deactivate_super(sb);
>  }
>  
> -EXPORT_SYMBOL(__mntput);
> -
>  /* iterator */
>  static void *m_start(struct seq_file *m, loff_t *pos)
>  {


  reply	other threads:[~2005-08-15  4:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15  1:53 [patch] unexport __mntput() Coywolf Qi Hunt
2005-08-15  4:07 ` Mike Waychison [this message]
2005-08-15  5:14   ` Coywolf Qi Hunt
2005-08-16 11:21   ` Jan Engelhardt
2005-08-16 17:13     ` Mike Waychison

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=430014EA.4030404@google.com \
    --to=mikew@google.com \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=coywolf@sosdg.org \
    --cc=linux-kernel@vger.kernel.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