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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1385590680-8110-1-git-send-email-henrik@austad.us>
Date:	Wed, 27 Nov 2013 23:18:00 +0100
From:	Henrik Austad <henrik@...tad.us>
To:	LKML doc <linux-doc@...r.kernel.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Henrik Austad <henrik@...tad.us>, Ingo Molnar <mingo@...e.hu>
Subject: [PATCH] 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.

Introduces in 2eec9ad9 (lightweight robust futexes: docs)

CC: Ingo Molnar <mingo@...e.hu>
Signed-off-by: Henrik Austad <henrik@...tad.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/