From: Mike Waychison <Michael.Waychison@Sun.COM>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: viro@parcelfarce.linux.theplanet.co.uk
Subject: [PATCH 2/2] vfsmount_lock / mnt_parent
Date: Mon, 26 Jan 2004 18:07:51 -0500 [thread overview]
Message-ID: <40159DC7.9080504@sun.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
The attached patch ensures that we grab vfsmount_lock when grabbing a
reference to mnt_parent in follow_up and follow_dotdot.
We also don't need to access ->mnt_parent in follow_mount and
__follow_down to mntput because we already the parent pointer on the stack.
--
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
mailto: Michael.Waychison@Sun.COM
http://www.sun.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[-- Attachment #2: follow_friends_vfsmount_lock.patch --]
[-- Type: text/x-patch, Size: 2026 bytes --]
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.1521 -> 1.1522
# fs/namei.c 1.87 -> 1.88
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 04/01/26 michael.waychison@sun.com 1.1522
# namei.c:
# - protect references to vfsmount->mnt_parent with vfsmount_lock
# --------------------------------------------
#
diff -Nru a/fs/namei.c b/fs/namei.c
--- a/fs/namei.c Mon Jan 26 21:39:45 2004
+++ b/fs/namei.c Mon Jan 26 21:39:45 2004
@@ -420,15 +420,15 @@
{
struct vfsmount *parent;
struct dentry *mountpoint;
- spin_lock(&dcache_lock);
+ spin_lock(&vfsmount_lock);
parent=(*mnt)->mnt_parent;
if (parent == *mnt) {
- spin_unlock(&dcache_lock);
+ spin_unlock(&vfsmount_lock);
return 0;
}
mntget(parent);
mountpoint=dget((*mnt)->mnt_mountpoint);
- spin_unlock(&dcache_lock);
+ spin_unlock(&vfsmount_lock);
dput(*dentry);
*dentry = mountpoint;
mntput(*mnt);
@@ -446,9 +446,9 @@
struct vfsmount *mounted = lookup_mnt(*mnt, *dentry);
if (!mounted)
break;
+ mntput(*mnt);
*mnt = mounted;
dput(*dentry);
- mntput(mounted->mnt_parent);
*dentry = dget(mounted->mnt_root);
res = 1;
}
@@ -464,9 +464,9 @@
mounted = lookup_mnt(*mnt, *dentry);
if (mounted) {
+ mntput(*mnt);
*mnt = mounted;
dput(*dentry);
- mntput(mounted->mnt_parent);
*dentry = dget(mounted->mnt_root);
return 1;
}
@@ -498,14 +498,16 @@
dput(old);
break;
}
+ spin_unlock(&dcache_lock);
+ spin_lock(&vfsmount_lock);
parent = (*mnt)->mnt_parent;
if (parent == *mnt) {
- spin_unlock(&dcache_lock);
+ spin_unlock(&vfsmount_lock);
break;
}
mntget(parent);
*dentry = dget((*mnt)->mnt_mountpoint);
- spin_unlock(&dcache_lock);
+ spin_unlock(&vfsmount_lock);
dput(old);
mntput(*mnt);
*mnt = parent;
next reply other threads:[~2004-01-26 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 23:07 Mike Waychison [this message]
2004-01-27 14:17 ` [PATCH 2/2] vfsmount_lock / mnt_parent Maneesh Soni
2004-01-27 15:23 ` raven
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=40159DC7.9080504@sun.com \
--to=michael.waychison@sun.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox