From: Christoph Hellwig <hch@infradead.org>
To: raven@themaw.net
Cc: Christoph Hellwig <hch@infradead.org>,
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-rc1-mm1
Date: Wed, 21 Apr 2004 14:18:30 +0100 [thread overview]
Message-ID: <20040421141829.A5551@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0404212022370.3740@donald.themaw.net>; from raven@themaw.net on Wed, Apr 21, 2004 at 08:31:38PM +0800
On Wed, Apr 21, 2004 at 08:31:38PM +0800, raven@themaw.net wrote:
> If it is decided to do this then would something like this be approiate
> Andrew?
>
> I have
> - renamed autofs4_may_umount to may_umount_tree and moved
> it to namespace.c
> - removed the EXPORT_SYMBOL for vfsmount_lock
> - updated autofs4 to suit
>
> It is not possible to merge the functionality of may_umount into this as,
> it stands, as autofs v3 requires a slightly different semantic. That is if
> there are submounts that are not busy then it should return -EBUSY but
> may_umount_tree would return not busy.
What about adding a paramter 'ignore_busy_submounts' and use most of the
function in common for both autofs3 and autofs4?
> + 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;
> +repeat:
> + next = this_parent->mnt_mounts.next;
> +resume:
> + while (next != &this_parent->mnt_mounts) {
> + struct vfsmount *p = list_entry(next, struct vfsmount, mnt_child);
> +
> + next = next->next;
Any chance to use list_for_each_entry here?
> + if ( !list_empty(&p->mnt_mounts) ) {
This wants a white-space fixup.
next prev parent reply other threads:[~2004-04-21 13:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 6:01 2.6.6-rc1-mm1 Andrew Morton
2004-04-19 6:29 ` 2.6.6-rc1-mm1 William Lee Irwin III
2004-04-19 6:42 ` 2.6.6-rc1-mm1 Andrew Morton
2004-04-19 6:49 ` 2.6.6-rc1-mm1 William Lee Irwin III
2004-04-19 7:06 ` 2.6.6-rc1-mm1 William Lee Irwin III
2004-04-19 18:39 ` bitmap, cpumask_arith (was: 2.6.6-rc1-mm1) Paul Jackson
2004-04-20 21:17 ` Paul Jackson
2004-04-20 21:38 ` William Lee Irwin III
2004-04-19 6:58 ` 2.6.6-rc1-mm1 Nick Piggin
2004-04-19 9:13 ` 2.6.6-rc1-mm1 failure: kmod.o didn't compile with module-less setup Helge Hafting
2004-04-19 9:17 ` Andrew Morton
2004-04-19 15:26 ` 2.6.6-rc1-mm1 (compile stats) John Cherry
2004-04-19 19:25 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-20 1:13 ` 2.6.6-rc1-mm1 Ian Kent
2004-04-20 1:26 ` 2.6.6-rc1-mm1 Andrew Morton
2004-04-21 9:08 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 12:31 ` 2.6.6-rc1-mm1 raven
2004-04-21 13:18 ` Christoph Hellwig [this message]
2004-04-21 13:34 ` 2.6.6-rc1-mm1 raven
2004-04-21 15:52 ` 2.6.6-rc1-mm1 raven
2004-04-21 16:09 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 12:39 ` 2.6.6-rc1-mm1 raven
2004-04-21 13:19 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 13:52 ` 2.6.6-rc1-mm1 raven
2004-04-21 14:56 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 15:39 ` 2.6.6-rc1-mm1 raven
2004-04-20 14:27 ` 2.6.6-rc1-mm1 raven
2004-04-20 15:06 ` 2.6.6-rc1-mm1 Rik van Riel
2004-04-21 7:37 ` 2.6.6-rc1-mm1 Sean Neakums
2004-04-21 12:16 ` 2.6.6-rc1-mm1 Hugh Dickins
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=20040421141829.A5551@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