From: Maneesh Soni <maneesh@in.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@digeo.com>,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
Dipankar Sarma <dipankar@in.ibm.com>,
Paul McKenney <Paul.McKenney@us.ibm.com>
Subject: Re: [patch 2/2] lockfree lookup_mnt
Date: Wed, 21 May 2003 14:56:05 +0530 [thread overview]
Message-ID: <20030521092605.GE1198@in.ibm.com> (raw)
In-Reply-To: <20030521092502.GD1198@in.ibm.com>
- Following patch uses synchronize_kernel in detach_mnt() and facilitates
lockless lookup_mnt.
- diff'ed over vfsmount_lock.patch
fs/namespace.c | 22 ++++++++++++++++++----
1 files changed, 18 insertions(+), 4 deletions(-)
diff -puN fs/namespace.c~lookup_mnt-rcu fs/namespace.c
--- linux-2.5.69/fs/namespace.c~lookup_mnt-rcu 2003-05-21 10:53:27.000000000 +0530
+++ linux-2.5.69-maneesh/fs/namespace.c 2003-05-21 10:56:57.000000000 +0530
@@ -74,6 +74,11 @@ void free_vfsmnt(struct vfsmount *mnt)
/*
* Now, lookup_mnt increments the ref count before returning
* the vfsmount struct.
+ *
+ * lookup_mnt can be done without taking any lock, as now we
+ * do synchronize_kernel() while removing vfsmount struct
+ * from mnt_hash list. rcu_read_(un)lock is required for
+ * pre-emptive kernels.
*/
struct vfsmount *lookup_mnt(struct vfsmount *mnt, struct dentry *dentry)
{
@@ -81,7 +86,7 @@ struct vfsmount *lookup_mnt(struct vfsmo
struct list_head * tmp = head;
struct vfsmount *p, *found = NULL;
- spin_lock(&vfsmount_lock);
+ rcu_read_lock();
for (;;) {
tmp = tmp->next;
p = NULL;
@@ -93,7 +98,7 @@ struct vfsmount *lookup_mnt(struct vfsmo
break;
}
}
- spin_lock(&vfsmount_lock);
+ rcu_read_unlock();
return found;
}
@@ -110,10 +115,19 @@ static void detach_mnt(struct vfsmount *
{
old_nd->dentry = mnt->mnt_mountpoint;
old_nd->mnt = mnt->mnt_parent;
+
+ /* remove from the hash_list, before other things */
+ list_del_rcu(&mnt->mnt_hash);
+ spin_unlock(&vfsmount_lock);
+
+ /* There could be existing users doing lookup_mnt, let
+ * them finish their work.
+ */
+ synchronize_kernel();
+ spin_lock(&vfsmount_lock);
mnt->mnt_parent = mnt;
mnt->mnt_mountpoint = mnt->mnt_root;
list_del_init(&mnt->mnt_child);
- list_del_init(&mnt->mnt_hash);
old_nd->dentry->d_mounted--;
}
@@ -121,7 +135,7 @@ static void attach_mnt(struct vfsmount *
{
mnt->mnt_parent = mntget(nd->mnt);
mnt->mnt_mountpoint = dget(nd->dentry);
- list_add(&mnt->mnt_hash, mount_hashtable+hash(nd->mnt, nd->dentry));
+ list_add_rcu(&mnt->mnt_hash, mount_hashtable+hash(nd->mnt, nd->dentry));
list_add_tail(&mnt->mnt_child, &nd->mnt->mnt_mounts);
nd->dentry->d_mounted++;
}
_
--
Maneesh Soni
IBM Linux Technology Center,
IBM India Software Lab, Bangalore.
Phone: +91-80-5044999 email: maneesh@in.ibm.com
http://lse.sourceforge.net/
next prev parent reply other threads:[~2003-05-21 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 9:25 [patch 1/2] vfsmount_lock Maneesh Soni
2003-05-21 9:26 ` Maneesh Soni [this message]
2003-05-21 9:35 ` Andrew Morton
2003-05-21 9:38 ` Paul Rolland
2003-05-21 9:43 ` Maneesh Soni
2003-05-21 9:45 ` [patch 2/2] lockfree lookup_mnt Maneesh Soni
2003-05-21 9:53 ` [patch 1/2] vfsmount_lock Dipankar Sarma
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=20030521092605.GE1198@in.ibm.com \
--to=maneesh@in.ibm.com \
--cc=Paul.McKenney@us.ibm.com \
--cc=akpm@digeo.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.