summaryrefslogtreecommitdiff
path: root/fs/bcachefs/six.h
diff options
context:
space:
mode:
authorRandy Dunlap <rdunlap@infradead.org>2023-12-09 22:06:44 -0800
committerKent Overstreet <kent.overstreet@linux.dev>2024-01-01 11:47:40 -0500
commitb56cee70e75e2edcbb92eb3d9357fae5df857b01 (patch)
treeb77b3b4bf18cbb67d162e83562bb4a0405471858 /fs/bcachefs/six.h
parentf8fd5871becf3beb7dff84c4608140a8c571c9a9 (diff)
bcachefs: six lock: fix typos
Fix a few typos in the six.h header file. Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Cc: Kent Overstreet <kent.overstreet@linux.dev> Cc: Brian Foster <bfoster@redhat.com> Cc: linux-bcachefs@vger.kernel.org Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'fs/bcachefs/six.h')
-rw-r--r--fs/bcachefs/six.h6
1 files changed, 3 insertions, 3 deletions
diff --git a/fs/bcachefs/six.h b/fs/bcachefs/six.h
index a7104ac1d35c..68d46fd7f391 100644
--- a/fs/bcachefs/six.h
+++ b/fs/bcachefs/six.h
@@ -15,7 +15,7 @@
* will have to take write locks for the full duration of the operation.
*
* But by adding an intent state, which is exclusive with other intent locks but
- * not with readers, we can take intent locks at thte start of the operation,
+ * not with readers, we can take intent locks at the start of the operation,
* and then take write locks only for the actual update to each individual
* nodes, without deadlocking.
*
@@ -65,8 +65,8 @@
*
* Reentrancy:
*
- * Six locks are not by themselves reentrent, but have counters for both the
- * read and intent states that can be used to provide reentrency by an upper
+ * Six locks are not by themselves reentrant, but have counters for both the
+ * read and intent states that can be used to provide reentrancy by an upper
* layer that tracks held locks. If a lock is known to already be held in the
* read or intent state, six_lock_increment() can be used to bump the "lock
* held in this state" counter, increasing the number of unlock calls that