From 9280379a7bf876ccde70040d6b7448b85c1e48f5 Mon Sep 17 00:00:00 2001 From: Ingo Weinhold Date: Mon, 20 Jun 2011 23:41:05 +0200 Subject: [PATCH] Comment typo fixes --- src/system/kernel/fs/vfs.cpp | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/system/kernel/fs/vfs.cpp b/src/system/kernel/fs/vfs.cpp index e1e1d0609c..d991e252ed 100644 --- a/src/system/kernel/fs/vfs.cpp +++ b/src/system/kernel/fs/vfs.cpp @@ -234,12 +234,12 @@ static recursive_lock sMountOpLock; private_node, mount) to which only read-only access is allowed. The mutable fields advisory_locking, mandatory_locked_by, and ref_count, as well as the busy, removed, unused flags, and the vnode's type can also be - write access when holding a read lock to sVnodeLock *and* having the vnode - locked. Writing access to covered_by requires to write lock sVnodeLock. + write accessed when holding a read lock to sVnodeLock *and* having the vnode + locked. Write access to covered_by requires to write lock sVnodeLock. The thread trying to acquire the lock must not hold sMountMutex. - You must not have this lock held when calling create_sem(), as this - might call vfs_free_unused_vnodes() and thus cause a deadlock. + You must not hold this lock when calling create_sem(), as this might call + vfs_free_unused_vnodes() and thus cause a deadlock. */ static rw_lock sVnodeLock = RW_LOCK_INITIALIZER("vfs_vnode_lock");