From: Henrik Austad <henrik@austad.us>
To: LKML doc <linux-doc@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Henrik Austad <henrik@austad.us>, Ingo Molnar <mingo@elte.hu>
Subject: [PATCH] Documentation/robust-futex-API: count properly to 4
Date: Wed, 27 Nov 2013 23:18:00 +0100 [thread overview]
Message-ID: <1385590680-8110-1-git-send-email-henrik@austad.us> (raw)
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
next reply other threads:[~2013-11-27 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 22:18 Henrik Austad [this message]
2013-11-30 13:42 ` [tip:core/locking] Documentation/robust-futex-API: Count properly to 4 tip-bot for Henrik Austad
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1385590680-8110-1-git-send-email-henrik@austad.us \
--to=henrik@austad.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).