aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems/directory-locking
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/filesystems/directory-locking')
-rw-r--r--Documentation/filesystems/directory-locking2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/filesystems/directory-locking b/Documentation/filesystems/directory-locking
index 34380d4fbce3..d7099a9266fb 100644
--- a/Documentation/filesystems/directory-locking
+++ b/Documentation/filesystems/directory-locking
@@ -82,7 +82,7 @@ own descendent. Moreover, there is exactly one cross-directory rename
Consider the object blocking the cross-directory rename. One
of its descendents is locked by cross-directory rename (otherwise we
-would again have an infinite set of of contended objects). But that
+would again have an infinite set of contended objects). But that
means that cross-directory rename is taking locks out of order. Due
to (2) the order hadn't changed since we had acquired filesystem lock.
But locking rules for cross-directory rename guarantee that we do not