From: Christoph Hellwig <hch@infradead.org>
To: raven@themaw.net
Cc: Andrew Morton <akpm@osdl.org>,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.6-rc2-mm1
Date: Fri, 23 Apr 2004 13:11:49 +0100 [thread overview]
Message-ID: <20040423131149.B1218@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0404222321310.6767@donald.themaw.net>; from raven@themaw.net on Thu, Apr 22, 2004 at 11:32:39PM +0800
On Thu, Apr 22, 2004 at 11:32:39PM +0800, raven@themaw.net wrote:
> +static int __may_umount_tree(struct vfsmount *mnt, int root_mnt_only)
> +{
> + struct list_head *next;
> + struct vfsmount *this_parent = mnt;
> + int actual_refs;
> + int minimum_refs;
> +
> + spin_lock(&vfsmount_lock);
> + actual_refs = atomic_read(&mnt->mnt_count);
> + minimum_refs = 2;
> +
> + if (root_mnt_only) {
> + spin_unlock(&vfsmount_lock);
> + if (actual_refs > minimum_refs)
> + return -EBUSY;
> + return 0;
Sorry for changing my opionin, but I somehow thought autofs3 could make
more use of this function. it it's really just a single atomic_read that's
shared it doesn't really make a lot of sense, does it?
next prev parent reply other threads:[~2004-04-23 12:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 8:45 2.6.6-rc2-mm1 Andrew Morton
2004-04-21 16:08 ` 2.6.6-rc2-mm1 raven
2004-04-22 15:32 ` 2.6.6-rc2-mm1 raven
2004-04-23 12:11 ` Christoph Hellwig [this message]
2004-04-23 13:33 ` 2.6.6-rc2-mm1 raven
2004-04-23 13:35 ` 2.6.6-rc2-mm1 Christoph Hellwig
2004-04-24 13:43 ` 2.6.6-rc2-mm1 raven
2004-04-22 18:55 ` 2.6.6-rc2-mm1 Alexander Gran
2004-04-25 1:20 ` [patch] 2.6.6-rc2-mm1: drm_irq.h has useless __NO_VERSION__ Adrian Bunk
2004-04-23 5:50 2.6.6-rc2-mm1 Frédéric L. W. Meunier
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=20040423131149.B1218@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=viro@parcelfarce.linux.theplanet.co.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
all inboxes | Powered by JetHome®