Hello Adrian,

please, include this patch to your tree.

From 6f20d2abd85874658ef424ac46b79c43244d2274 Mon Sep 17 00:00:00 2001
From: Artem Bityutskiy <[EMAIL PROTECTED]>
Date: Mon, 9 Apr 2007 14:23:48 +0300
Subject: [PATCH] trivial: s/i_sem /i_mutex/

This patch substitutes i_sem by i_mutex in Documentation/filesystems/Locking.
The patch also removes a couple of trailing white-spaces.

Signed-off-by: Artem Bityutskiy <[EMAIL PROTECTED]>
---
Documentation/filesystems/Locking |   10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/Documentation/filesystems/Locking 
b/Documentation/filesystems/Locking
index 28bfea7..6bb5706 100644
--- a/Documentation/filesystems/Locking
+++ b/Documentation/filesystems/Locking
@@ -21,12 +21,12 @@ locking rules:
                dcache_lock     rename_lock     ->d_lock     may block
d_revalidate:   no              no              no              yes
d_hash          no              no              no              yes
-d_compare: no yes no no +d_compare: no yes no no
d_delete:       yes             no              yes             no
d_release:      no              no              no              yes
d_iput:         no              no              no              yes

---------------------------- inode_operations --------------------------- +--------------------------- inode_operations ---------------------------
prototypes:
        int (*create) (struct inode *,struct dentry *,int, struct nameidata *);
        struct dentry * (*lookup) (struct inode *,struct dentry *, struct nameid
@@ -52,7 +52,7 @@ ata *);

locking rules:
        all may block, none have BKL
-               i_sem(inode)
+               i_mutex(inode)
lookup:         yes
create:         yes
link:           yes (both)
@@ -72,7 +72,7 @@ setxattr:     yes
getxattr:       no
listxattr:      no
removexattr:    yes
-       Additionally, ->rmdir(), ->unlink() and ->rename() have ->i_sem on
+       Additionally, ->rmdir(), ->unlink() and ->rename() have ->i_mutex on
victim.
        cross-directory ->rename() has (per-superblock) ->s_vfs_rename_sem.
        ->truncate() is never called directly - it's a callback, not a
@@ -459,7 +459,7 @@ doesn't take the BKL.
->read on directories probably must go away - we should just enforce -EISDIR
in sys_read() and friends.

-->fsync() has i_sem on inode.
+->fsync() has i_mutex on inode.

--------------------------- dquot_operations -------------------------------
prototypes:
--
1.5.0.6


--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to