Commit b56cee70 authored by Randy Dunlap's avatar Randy Dunlap Committed by Kent Overstreet

bcachefs: six lock: fix typos

Fix a few typos in the six.h header file.
Signed-off-by: default avatarRandy 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: default avatarKent Overstreet <kent.overstreet@linux.dev>
parent f8fd5871
...@@ -15,7 +15,7 @@ ...@@ -15,7 +15,7 @@
* will have to take write locks for the full duration of the operation. * 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 * 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 * and then take write locks only for the actual update to each individual
* nodes, without deadlocking. * nodes, without deadlocking.
* *
...@@ -65,8 +65,8 @@ ...@@ -65,8 +65,8 @@
* *
* Reentrancy: * Reentrancy:
* *
* Six locks are not by themselves reentrent, but have counters for both the * Six locks are not by themselves reentrant, but have counters for both the
* read and intent states that can be used to provide reentrency by an upper * 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 * 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 * 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 * held in this state" counter, increasing the number of unlock calls that
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment