linux-kernel - [PATCH 0/5] Futex cleanups and race fix

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]

Date:	Mon, 21 Sep 2009 22:29:52 -0700
From:	Darren Hart <dvhltc@...ibm.com>
To:	linux-kernel@...r.kernel.org
Subject: [PATCH 0/5] Futex cleanups and race fix

The following series corrects several innacurate comments in the futex code as
well as reformat some of the existing comments to be mostly consistent
throughout futex.c. The final patch fixes a nasty little race in the requeue pi
code resulting in missed wakeups and hung userspace application threads.

Signed-off-by: Darren Hart <dvhltc@...ibm.com>
Cc: Thomas Gleixner <tglx@...utronix.de>
Cc: Peter Zijlstra <peterz@...radead.org>
Cc: Steven Rostedt <rostedt@...dmis.org>
Cc: Ingo Molnar <mingo@...e.hu>
CC: Eric Dumazet <eric.dumazet@...il.com>
CC: Dinakar Guniguntala <dino@...ibm.com>
CC: John Stultz <johnstul@...ibm.com>

---

Darren Hart (5):
      futex: fix wakeup race by setting TASK_INTERRUPTIBLE before queue_me
      futex: correct futex_q woken state commentary
      futex: make function kernel-doc commentary consistent
      futex: correct queue_me and unqueue_me commentary
      futex: correct futex_wait_requeue_pi() commentary


 kernel/futex.c |  135 ++++++++++++++++++++++++++++++--------------------------
 1 files changed, 72 insertions(+), 63 deletions(-)

-- 
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
--
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/