aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/robust-futex-ABI.txt
diff options
context:
space:
mode:
authorHenrik Austad <henrik@austad.us>2013-11-27 17:18:00 -0500
committerIngo Molnar <mingo@kernel.org>2013-11-30 08:08:28 -0500
commit854ff82ab085aed7509f6fb90f79ce6c41ee1fa4 (patch)
treed083496dcc5d611706793b2a7882627f6d15a1ec /Documentation/robust-futex-ABI.txt
parent1acd437c59c7dd78d8f1e5f07bea6a18b7b5cd77 (diff)
Documentation/robust-futex-API: Count properly to 4
A strictly monotonically increasing sequence is normally used in numbered lists as they provide an intuitive ordering of the elements. However, in situations where race conditions can appear, this assumption breaks down and you can end up with unpredictable results, leading to a rather confusing list :-) This changes the numbered list 1,2,2,2 to the more intuitive 1,2,3,4. Introduced in: 2eec9ad91f71 [PATCH] lightweight robust futexes: docs Signed-off-by: Henrik Austad <henrik@austad.us> Link: http://lkml.kernel.org/r/1385590680-8110-1-git-send-email-henrik@austad.us Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'Documentation/robust-futex-ABI.txt')
-rw-r--r--Documentation/robust-futex-ABI.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/robust-futex-ABI.txt b/Documentation/robust-futex-ABI.txt
index fd1cd8aae4eb..16eb314f56cc 100644
--- a/Documentation/robust-futex-ABI.txt
+++ b/Documentation/robust-futex-ABI.txt
@@ -146,8 +146,8 @@ On removal:
146 1) set the 'list_op_pending' word to the address of the 'lock entry' 146 1) set the 'list_op_pending' word to the address of the 'lock entry'
147 to be removed, 147 to be removed,
148 2) remove the lock entry for this lock from the 'head' list, 148 2) remove the lock entry for this lock from the 'head' list,
149 2) release the futex lock, and 149 3) release the futex lock, and
150 2) clear the 'lock_op_pending' word. 150 4) clear the 'lock_op_pending' word.
151 151
152On exit, the kernel will consider the address stored in 152On exit, the kernel will consider the address stored in
153'list_op_pending' and the address of each 'lock word' found by walking 153'list_op_pending' and the address of each 'lock word' found by walking