[PATCH] Documentation/robust-futex-API: count properly to 4

[PATCH] Documentation/robust-futex-API: count properly to 4

[Henrik Austad]

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.

Introduces in 2eec9ad9 (lightweight robust futexes: docs)

CC: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Henrik Austad <henrik@austad.us>
---
 Documentation/robust-futex-ABI.txt |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/robust-futex-ABI.txt b/Documentation/robust-futex-ABI.txt
index fd1cd8a..16eb314 100644
--- a/Documentation/robust-futex-ABI.txt
+++ b/Documentation/robust-futex-ABI.txt
@@ -146,8 +146,8 @@ On removal:
  1) set the 'list_op_pending' word to the address of the 'lock entry'
     to be removed,
  2) remove the lock entry for this lock from the 'head' list,
- 2) release the futex lock, and
- 2) clear the 'lock_op_pending' word.
+ 3) release the futex lock, and
+ 4) clear the 'lock_op_pending' word.
 
 On exit, the kernel will consider the address stored in
 'list_op_pending' and the address of each 'lock word' found by walking
-- 
1.7.10.4

[tip:core/locking] Documentation/robust-futex-API: Count properly to 4

[tip-bot for Henrik Austad]

Commit-ID:  854ff82ab085aed7509f6fb90f79ce6c41ee1fa4
Gitweb:     http://git.kernel.org/tip/854ff82ab085aed7509f6fb90f79ce6c41ee1fa4
Author:     Henrik Austad <henrik@austad.us>
AuthorDate: Wed, 27 Nov 2013 23:18:00 +0100
Committer:  Ingo Molnar <mingo@kernel.org>
CommitDate: Sat, 30 Nov 2013 14:08:28 +0100

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>
---
 Documentation/robust-futex-ABI.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/robust-futex-ABI.txt b/Documentation/robust-futex-ABI.txt
index fd1cd8a..16eb314f 100644
--- a/Documentation/robust-futex-ABI.txt
+++ b/Documentation/robust-futex-ABI.txt
@@ -146,8 +146,8 @@ On removal:
  1) set the 'list_op_pending' word to the address of the 'lock entry'
     to be removed,
  2) remove the lock entry for this lock from the 'head' list,
- 2) release the futex lock, and
- 2) clear the 'lock_op_pending' word.
+ 3) release the futex lock, and
+ 4) clear the 'lock_op_pending' word.
 
 On exit, the kernel will consider the address stored in
 'list_op_pending' and the address of each 'lock word' found by walking