All of lore.kernel.org
 help / color / mirror / Atom feed
From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Mike Waychison <mikew@google.com>
Cc: coywolf@sosdg.org, akpm@osdl.org, bunk@stusta.de,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] unexport __mntput()
Date: Mon, 15 Aug 2005 13:14:22 +0800	[thread overview]
Message-ID: <2cd57c9005081422143b0f2717@mail.gmail.com> (raw)
In-Reply-To: <430014EA.4030404@google.com>

On 8/15/05, Mike Waychison <mikew@google.com> wrote:
> 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

Yes, indeed.

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

And more than above, there's more stuff depend on it, af_unix, ipc
message queues, etc.

Thanks for your help.
-- 
Coywolf Qi Hunt
http://ahbl.org/~coywolf/

  reply	other threads:[~2005-08-15  5:14 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
2005-08-15  5:14   ` Coywolf Qi Hunt [this message]
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=2cd57c9005081422143b0f2717@mail.gmail.com \
    --to=coywolf@gmail.com \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=coywolf@sosdg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikew@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.